Got an ANR(Application Not Responding) error about mapbox-search-android HOT 8 CLOSED

would love to get some help with this, ASAP(during work hours) as this might be blocking development. 🙏🏼

from mapbox-search-android.

Hey @LaurieWuAndroid,
Very sorry to hear that you've faced with this issue.

As I see, you're using quite an old version of Maps SDKv9.6.1 and we don't guarantee compatibility with the new Search SDK.

Will you be able to migrate to Maps v10 and pick one of the latest versions of the Maps SDK https://github.com/mapbox/mapbox-maps-android/releases?

Also, I'm curious why are you initializing Search SDK on a IO dispatcher? Any reason for that?

        applicationScope.launch(dispatcher.io()) {
            MapboxSearchSdk.initialize(
                this@HatchApplication,
                getString(hatch.features.rewards.R.string.mapbox_access_token),
                DefaultLocationProvider(this@HatchApplication)
            )
        }

from mapbox-search-android.

Hi @DzmitryFomchyn thanks for the speedy response! I tried to switch to higher mapbox version(10.2.0, 10.5.0), it results in build error Unable to make private void java.util.concurrent.CopyOnWriteArrayList.writeObject(java.io.ObjectOutputStream) throws java.io.IOException accessible: module java.base does not "opens java.util.concurrent" to unnamed module @29fc2153

In response to your question on IO dispatcher, we're trying to init the sdk off the main thread, so that process doesn't block user input and freeze the app.

from mapbox-search-android.

Unable to make private void java.util.concurrent.CopyOnWriteArrayList.writeObject(java.io.ObjectOutputStream) throws java.io.IOException accessible: module java.base does not "opens java.util.concurrent" to unnamed module @29fc2153

Hmm, that's a very strange bug and we haven't seen this before in any of Mapbox SDKs. Could you please share a full error log? Also, it would be very helpful if you could share a test project that shows this bug.

In response to your question on IO dispatcher, we're trying to init the sdk off the main thread, so that process doesn't block user input and freeze the app

Did you notice that Search SDK initialization slows down app startup?

from mapbox-search-android.

Hmm, that's a very strange bug and we haven't seen this before in any of Mapbox SDKs. Could you please share a full error log? Also, it would be very helpful if you could share a test project that shows this bug.

We had to revert a chunk of code for now to unblock development, thus this issue is not as urgent now. I love the idea, though not sure if my schedule allows. I will try my best to follow up on this as I find more info.

Did you notice that Search SDK initialization slows down app startup?

Not that I noticed, since this code was already implemented, but it is also good practice to have any initialization that might take a long time to be in the background thread.

from mapbox-search-android.

I will try my best to follow up on this as I find more info.

@LaurieWuAndroid should we close it for now then? Feel free to reopen as new info is encountered.

from mapbox-search-android.

I will try my best to follow up on this as I find more info.

@LaurieWuAndroid should we close it for now then? Feel free to reopen as new info is encountered.

I'm okay with that 😃, thank you!

from mapbox-search-android.

I'm closing the issue. Feel free to reopen it or create a new one if you have more questions.

from mapbox-search-android.