OfflineMode issues when connected to internal network

[logananderson]

Platform: Android
Mapbox SDK version: 4.2.0

Steps to trigger behavior

1. Implement offline maps and download region.
2. Turn off internet, connect to internal network via dhcp
3. Notice timeouts/exceptions on network calls

I apologize for my lack of knowledge here. I'm an iOS developer by trade.

Currently using MapBox in Offline mode to serve up tablet apps in a consumer setting. We use wired lan connection to interact with our local server. There is no internet connection.

Everything works fine, but often we get a freeze until I see
08-15 17:04:24.807 25874-26015/com.getcruise.avt.display E/MapboxEventManager: FlushTheEventsTask borked: java.net.SocketTimeoutException: failed to connect to events.mapbox.com/52.207.190.25 (port 443) after 10000ms

In like 631 of MapboxEventManager.java, it looks like our situation is getting passed your connectivity check, (and I imagine elsewhere too) as I see in the logs an incredible amount of timeouts. Is there any way to force mapbox to recognize offline status and not attempt to make calls over our internal network?

[cammace]

Hey there, looks like this issue slipped through the cracks. Can you confirm that this issue has been resolved using the latest 4.2.0-beta.4. We've recently made a few fixes to the behavior of offline including #6293

[cammace]

Ticket hasn't been updated, if you are still running into this issue, I'll be happy to open this ticket back up. Feel free to reach out on Stack Overflow or through our contact page if you have any additional questions.

[logananderson]

Hey! We actually ended up editing the source code for a little while to prevent the crash. In the end, we started supporting more cities so it was in our best interest to have internet as well, rather than try and manage many different offline regions. We've switched back to using the unmodified android source. I appreciate your attention on this.