You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running our release-candidate APK on BrowserStack, the Mapbox style fails to load and we receive HTTP 502 errors in the logs.
To Reproduce
Build the app with our release-candidate profile (not the test profile) and upload the APK to BrowserStack
Open the app in a BrowserStack device session.
Observe that the map never fully loads and continues to show errors in the logs.
Expected behavior
The map style should successfully load, displaying the custom layers and icons. Instead, the map surfaces repeated HTTP 502 errors when it tries to fetch the style.
Screenshots
Here you can see that the icons don't load either.
Smartphone (please complete the following information):
Device/Platform on BrowserStack: e.g. Samsung Galaxy S22 w/ Android 12
Additional context
Even after enabling Local Testing in BrowserStack, the device still returns 502 when requesting our internal style endpoint.
After some checking via logging, the Fastify server is definitely starting appropriately and is not stopping early.
Guesses
The on-device Node Server seems like it might not be responding?
The text was updated successfully, but these errors were encountered:
Describe the bug
When running our release-candidate APK on BrowserStack, the Mapbox style fails to load and we receive HTTP 502 errors in the logs.
To Reproduce
Expected behavior
The map style should successfully load, displaying the custom layers and icons. Instead, the map surfaces repeated HTTP 502 errors when it tries to fetch the style.
Screenshots

Here you can see that the icons don't load either.
Smartphone (please complete the following information):
Additional context
Logs and Observations
Here is a link to the full device logs from Browserstack
The logs in Browserstack show that the style URL returns a 502:
Relevant References
BrowserStack docs on managing local / internal connections
The style is hosted on a localhost endpoint. Here are the docs I found: https://www.browserstack.com/docs/app-automate/appium/test-on-internal-network/manage-incoming-connections
Additional context
Even after enabling Local Testing in BrowserStack, the device still returns 502 when requesting our internal style endpoint.
After some checking via logging, the Fastify server is definitely starting appropriately and is not stopping early.
Guesses
The on-device Node Server seems like it might not be responding?
The text was updated successfully, but these errors were encountered: