Navigation UI offroute stuck fetching new route.

[BinaryPigStudio]

(...)
@Override
public boolean allowRerouteFrom(Point offRoutePoint)
{
    return true;
}
(...)

NavigationRoute.builder(getContext()).accessToken(getString(R.string.mapbox_access_token)).origin(origin).destination(destination).enableRefresh(true).build().getRoute(new Callback<DirectionsResponse>()
        {
            @Override
            public void onResponse(Call<DirectionsResponse> call, Response<DirectionsResponse> response)
            {
                if (response.body() == null || response.body().routes().isEmpty())
                    return;

                startNavigation(response.body().routes().get(0));
            }

            @Override
            public void onFailure(Call<DirectionsResponse> call, Throwable t)
            {
                Timber.e(t);
            }
        });

Navigation UI SDK re routing works on most API and CPU but on the 'Cortex-A55' the re-routing is not completed, instead, it crashes the app by being stuck for too long.

**Android API: 29
**Mapbox Navigation UI SDK version: 0.42.0

Steps to trigger behavior

1. Go off course.
2. Wait for rerouting

Expected behavior

After going off course, a new route would be fetched and drawn from the point where the user is currently in.

Actual behavior

After going off course, the listeners are triggered but a new route is not fetched, crashing the app.

Is this a bug for this kind of CPU or a poor implementation of the SDK?

Thank you
Tiago from Binary Pig

[Guardiola31337]

@abhishek1508 @JunDai is this still an issue in 1.0?

[abhishek1508]

As mentioned that it functions well for other devices except Cortex-A55 sharing the crash logs would be great to dig deeper.
cc @BinaryPigStudio

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[timmytreen7]

I didn't know that. I was in the hospital and I just got out