On Monday, 11 March 2019 13:08:50 UTC+1, Harry van der Wolf wrote:
>
> Fdroid always compile their own versions and often run 2-3 subversions
> behind. Yalp downloads "somehow" from the Play Store without using the
> Google framework. I have no idea how that works and if the beta channel is
>
Fdroid always compile their own versions and often run 2-3 subversions
behind. Yalp downloads "somehow" from the Play Store without using the
Google framework. I have no idea how that works and if the beta channel is
fully supported.
There are more third party options that simply sideload apks
>
> I don't see that version 3.3.4 in F-Droid nor via Yalp. The most recent
> version I can get my hands on is 3.3.3. Cleargin the data, clearing the
> cache, removing and re-installing that version does not fix the issue.
> Perhaps it is fixed with installing 3.3.4, but I can't get to that
Op maandag 11 maart 2019 10:44:54 UTC+1 schreef Harry van der Wolf:
>
> Your apk is missing an image from its resources. It is one of the images
> on the main screen (mapactivity) used on buttons, like the globe or the
> compass or the magnifying glass or whatever image on a button.
> It
Op maandag 11 maart 2019 09:57:51 UTC+1 schreef Max1234Ita:
>
> I see this:
>
>> Caused by: android.view.InflateException: Binary XML file line #173:
>> Error inflating class ImageButton
>
>
>
> I'm not a OsmAnd developer, but this seems to be related to some error in
> the apk you
Your apk is missing an image from its resources. It is one of the images on
the main screen (mapactivity) used on buttons, like the globe or the
compass or the magnifying glass or whatever image on a button.
It simply means that your apk is not correct, or that the dalvik app cache
was not correct
I see this:
> Caused by: android.view.InflateException: Binary XML file line #173:
> Error inflating class ImageButton
I'm not a OsmAnd developer, but this seems to be related to some error in
the apk you downloaded.
Did you already try to re-download, uninstall and reinstall the app?
Below is, I believe, relevant logcat information:
03-08 10:07:18.941 15112 15112 E AndroidRuntime: FATAL EXCEPTION: main
03-08 10:07:18.941 15112 15112 E AndroidRuntime: Process: net.osmand, PID:
15112
03-08 10:07:18.941 15112 15112 E AndroidRuntime: java.lang.RuntimeException:
Unable to start
Can you post your adb log? You may wish to redact some items.
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to osmand+unsubscr...@googlegroups.com.
For more options,
it all permissions I could (microfone, storage,
location, phone and camera). Same result.
> Max
>
>
> On Friday, March 8, 2019 at 10:28:56 AM UTC+1, NHV wrote:
>>
>> Updated to version 3.3.3 yesterday.
>>
>> When trying to open the app, OSMAnd crashes immediat
trying to open the app, OSMAnd crashes immediately. Remove and
> re-install does not solve the issue.
>
> Running Android 6.0 on non-rooted LG G3.
>
> Any pointers are welcome.
>
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
Updated to version 3.3.3 yesterday.
When trying to open the app, OSMAnd crashes immediately. Remove and
re-install does not solve the issue.
Running Android 6.0 on non-rooted LG G3.
Any pointers are welcome.
--
You received this message because you are subscribed to the Google Groups
12 matches
Mail list logo
