Vendetta just crashing without doing anything.

[Yozzen]

Using a Samsung Galaxy A13
One UI v5.1
Android v13

After rebooting my phone this crash issue also appeared after I reinstalled discord v200.13 then I install beta or alpha but same issue.

[skdaddles]

Hey! I have the exact same phone! fully updated! Same problem here, it was working and after my phone ran out of battery, i cannot launch the app. It opens, does the loading like for every app and then it crashes. Idk what's going on but its no good.

[Brian2po]

I have the same problem, it just crashes, my theory here is that the latest discord update broke all of the modded client. We will just have to patiently wait for the fix.

[maisymoe]

Likely caused by NoTrack, I'll disable it for now and look at fixing it again later.

[nexpid]

turns out NoTrack was the source of my crashing too lol

[Yozzen]

@maisymoe Please fix it soon because I'm missing vendetta🥺🥺

[nexpid]

@maisymoe Please fix it soon because I'm missing vendetta🥺🥺

did you try uninstalling NoTrack (if you even had it installed)

[Yozzen]

@maisymoe Please fix it soon because I'm missing vendetta🥺🥺

did you try uninstalling NoTrack (if you even had it installed)

I have not installed NoTrack

[1Lucas1apk]

Using a Samsung Galaxy A13
One UI v5.1
Android v13

After rebooting my phone this crash issue also appeared after I reinstalled discord v200.13 then I install beta or alpha but same issue.

Mine is the same thing, I managed to catch the error:

Error: FATAL EXCEPTION: create_react_context
Process: dev.beefers.vendetta, PID: 15747
java.lang.UnsatisfiedLinkError: No implementation found for void com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(android.content.res.AssetManager, java.lang.String, boolean) (tried Java_com_facebook_react_bridge_CatalystInstanceImpl_jniLoadScriptFromAssets and Java_com_facebook_react_bridge_CatalystInstanceImpl_jniLoadScriptFromAssets__Landroid_content_res_AssetManager_2Ljava_lang_String_2Z) - is the library loaded, e.g. System.loadLibrary?
at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
at java.lang.reflect.Method.invoke(Native Method)
at org.lsposed.lspd.nativebridge.HookBridge.invokeOriginalMethod(Native Method)
at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(XposedBridge.java:474)
at LSPHooker_.jniLoadScriptFromAssets(Unknown Source:21)
at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(SourceFile:3)
at com.facebook.react.bridge.JSBundleLoader$1.loadScript(SourceFile:11)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(SourceFile:19)
at com.facebook.react.ReactInstanceManager.createReactContext(SourceFile:224)
at com.facebook.react.ReactInstanceManager.i(Unknown Source:0)
at com.facebook.react.ReactInstanceManager$5.run(SourceFile:70)
at java.lang.Thread.run(Thread.java:1012)

[1Lucas1apk]

Mine is Samsung A13 (Both 5G and without, I have both devices) Android 13, One UI 5.1

[1Lucas1apk]

Application I used to catch errors (Scoop) :)

[Yozzen]

Why are you not solving this problem?
@nexpid @maisymoe

[maisymoe]

Why are you not solving this problem?

Don't own the device, and the bug should never even occur in the first place. A device update is also more than likely to fix this in future.