Continuing the discussion from Feedback for v1.12.3 - Post #177:
In your post @dexic you have attributed the error to GPS, which seems a reasonable assumption. It is above my pay grade to fully explain the long log in your image however I have an observation.
I see:
LocationSource(com.google.android.gms:play-services-maps@@18.0.0:2)
…
JavaLangNullPointerException: Listener must not be null at …(similar)
Checking out
https://developers.google.com/android/reference/com/google/android/gms/maps/LocationSource [1]
public interface
LocationSource
Defines an interface for providing location data, typically to a GoogleMap object.
Further down the page if listener is null this will cause IllegalArgumentException as seen in your Critical Error notice.
So, if I read this right, it would seem that this app effectively requires official Google.
However, quoting again from [1], the app developers would seem to have the chance to remedy this:
A GoogleMap object has a built-in location provider for its my-location layer, but it can be replaced with another one that implements this interface.
Like … GPS coordinates should work. I am not certain of this but, my understanding / guess is that “failing to find GPS” or any provided alternative to Google would not cause IllegalArgumentException.
Developer contact is seen at https://play.google.com/store/apps/details?id=com.digitalchargingsolutions.vwfs.chargeandfuel&hl=en&gl=US
website https://www.chargeandfuel.vwfs.com/
email chargeandfuel@logpay.de
I hope you feel it worthwhile to send the log to the devs.
- (Is it possible you can get a test based copy of the log here, then perhaps someone will correct me if I jumped to wrong conclusions?)