[BUG] - New v3.2.0+ WPA crashes on start (Android 7)

[gitolicious]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

I have an ancient Android tablet which is solely used as a digital cook book. It is running Android 7.1.2 (LieneageOS 14.1) which is way outdated. Still, it was working fine with the pre-v3.2.0 PWA. Now, the PWA crashes on start. The web version is working fine.

Sure, this Android version is out of support, but maybe someone knows a quick and easy fix to get it back up and running.

Steps to Reproduce

1. start WPA on Android 7

Please provide relevant logs

adb logcat

Failed to open dex file '/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk' from memory: Unrecognized version number in /data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk: 0 3 8

Full log:

10-04 15:47:21.820 2666 5068 I ActivityManager: Start proc 6088:org.chromium.webapk.a3950655f905423e6_v2/u0a75 for activity org.chromium.webapk.a3950655f905423e6_v2/org.chromium.webapk.shell_apk.h2o.H2OOpaqueMainActivity
10-04 15:47:21.921 6088 6088 W art : Failed to open dex file '/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk' from memory: Unrecognized version number in /data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk: 0 3 8
10-04 15:47:21.923 6088 6088 W System : ClassLoader referenced unknown path: /data/app/org.chromium.webapk.a3950655f905423e6_v2-1/lib/arm
10-04 15:47:21.954 6088 6088 D AndroidRuntime: Shutting down VM
10-04 15:47:21.958 6088 6088 E AndroidRuntime: FATAL EXCEPTION: main
10-04 15:47:21.958 6088 6088 E AndroidRuntime: Process: org.chromium.webapk.a3950655f905423e6_v2, PID: 6088
10-04 15:47:21.958 6088 6088 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider org.chromium.webapk.shell_apk.h2o.SplashContentProvider: java.lang.ClassNotFoundException: Didn't find class "org.chromium.webapk.shell_apk.h2o.SplashContentProvider" on path: DexPathList[[zip file "/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk"],nativeLibraryDirectories=[/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/lib/arm, /system/lib, /vendor/lib]]
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5923)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.installContentProviders(ActivityThread.java:5490)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5429)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.-wrap2(ActivityThread.java)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1564)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6186)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "org.chromium.webapk.shell_apk.h2o.SplashContentProvider" on path: DexPathList[[zip file "/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk"],nativeLibraryDirectories=[/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/lib/arm, /system/lib, /vendor/lib]]
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5908)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: ... 10 more
10-04 15:47:21.958 6088 6088 E AndroidRuntime: Suppressed: java.io.IOException: Failed to open dex files from /data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk because: Failed to open dex file '/data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk' from memory: Unrecognized version number in /data/app/org.chromium.webapk.a3950655f905423e6_v2-1/base.apk: 0 3 8
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexFile.openDexFileNative(Native Method)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexFile.openDexFile(DexFile.java:367)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexFile.(DexFile.java:112)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexFile.(DexFile.java:77)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexPathList.loadDexFile(DexPathList.java:359)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexPathList.makeElements(DexPathList.java:323)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexPathList.makeDexElements(DexPathList.java:263)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.DexPathList.(DexPathList.java:126)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.(BaseDexClassLoader.java:48)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at dalvik.system.PathClassLoader.(PathClassLoader.java:64)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at com.android.internal.os.PathClassLoaderFactory.createClassLoader(PathClassLoaderFactory.java:43)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:58)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:520)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.LoadedApk.getClassLoader(LoadedApk.java:553)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:1885)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.LoadedApk.getResources(LoadedApk.java:766)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ContextImpl.(ContextImpl.java:2038)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ContextImpl.createAppContext(ContextImpl.java:1983)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5339)
10-04 15:47:21.958 6088 6088 E AndroidRuntime: ... 8 more

Mealie Version

demo.mealie.io:
Build: a4a6d4d

Local installation:
Image: ghcr.io/mealie-recipes/mealie:latest
Version: v3.3.1
Build: c63932e

Deployment

Docker (Linux)

Additional Deployment Details

No response

[Andrew-T-Smith]

Does this just present as a white screen on the tablet? If so, I am seeing the same thing on my iPad, but I am running v3.3.0.

Trying on v3.3.1, still having the same issue.

Going back to v3.1.2 (just randomly chosen), works again.

[michael-genson]

Looked into this a bit and unfortunately it doesn't seem like there's anything we can do about this. Specifically:

Unrecognized version number in .../base.apk: 0 3 8

This means that, for whatever reason, something is requiring Android v 8 (that's the "8" in 038). Looks like you'd have to upgrade the Android version of your device to at least Android 8.

I don't know what specifically is requiring Android 8 but it's probably related to Node which was upgraded in the latest version of Mealie (from Node 20 -> 22). If not Node directly, some dependency we're using that changed when we updated to Node 22.

[michael-genson]

Going to convert this to a discussion since I don't want to just close it and leave you SOL, but I don't want to keep it open as an issue since we can't really fix it.