[Bug] App is crashing on first launch

[harshitshah4]

Steps to reproduce/复现步骤

1. Used lspatch-release.jar from latest build actions
2. java -jar /Users/harshitshah/Downloads/LSPatch\ release\ 99c7435/jar-v0.6-418-release.jar ~/Downloads/sample.apk -m flag_secure.apk

On re-launching app it worked fine

Expected behaviour/预期行为

Crash on first launch

Actual behaviour/实际行为

Should not crash

Xposed Module List/Xposed 模块列表

flag_secure

LSPatch version/LSPatch 版本

99c7435 jar-v0.6-418-release.jar

Android version/Android 版本

15 Beta

Shizuku version/Shizuku 版本

N/A

Version requirement/版本要求

• [X] I am using latest debug CI version of LSPatch and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Apk file/Apk 文件

No response

Logs/日志

``` 09-04 05:26:47.311 E/AndroidRuntime(18777): FATAL EXCEPTION: main09-04 05:26:47.311 E/AndroidRuntime(18777): Process: com.example.all_in_one, PID: 1877709-04 05:26:47.311 E/AndroidRuntime(18777): java.lang.ExceptionInInitializerError09-04 05:26:47.311 E/AndroidRuntime(18777): at org.lsposed.lspatch.metaloader.LSPAppComponentFactoryStub.a(Unknown Source:446)09-04 05:26:47.311 E/AndroidRuntime(18777): at org.lsposed.lspatch.metaloader.LSPAppComponentFactoryStub.(Unknown Source:22)09-04 05:26:47.311 E/AndroidRuntime(18777): at java.lang.Class.newInstance(Native Method)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.LoadedApk.createAppFactory(LoadedApk.java:272)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:1043)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.LoadedApk.getClassLoader(LoadedApk.java:1134)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.LoadedApk.getResources(LoadedApk.java:1382)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ContextImpl.createAppContext(ContextImpl.java:3399)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ContextImpl.createAppContext(ContextImpl.java:3390)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7375)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2415)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.os.Handler.dispatchMessage(Handler.java:107)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.os.Looper.loopOnce(Looper.java:232)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.os.Looper.loop(Looper.java:317)09-04 05:26:47.311 E/AndroidRuntime(18777): at android.app.ActivityThread.main(ActivityThread.java:8699)09-04 05:26:47.311 E/AndroidRuntime(18777): at java.lang.reflect.Method.invoke(Native Method)09-04 05:26:47.311 E/AndroidRuntime(18777): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)09-04 05:26:47.311 E/AndroidRuntime(18777): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:886)09-04 05:26:47.311 E/AndroidRuntime(18777): Caused by: java.lang.NoClassDefFoundError: Class not found using the boo ```

[JingMatrix]

Please allow me to first remind you that, if you checked the option:

I am using latest debug CI version of LSPatch and enable verbose log

, then you should use the debug version for reporting the issue.

Please upload new logs, if possible, with command:

adb logcat -s AndroidRuntime LSPatch LSPosed LSPatch-MetaLoader LSPatch-SigBypass LSPosed-Bridge LSPlant LSPosedContext zygisk64 LSPlt Dobby LSPosedService '*:F'

[skxev]

Hi, I have the same problem after the August Google Play system update, I am using latest debug CI version of LSPatch and enable verbose log

[skxev]

Starting logcat and open app when crash

[harshitshah4]

@JingMatrix Apologies for not attaching debug logs. Just sharing additional information, I tested this with previous commit: b8c4664 jar-v0.6-419-release.jar, and the app no longer crashed

[JingMatrix]

Bug comfirmed, should be fixed in b409cd3. Please tell me if the latest build didn't remove this bug, thanks for reporting.