When you sign an APK it creates a new signed apk. You tried to install app-universal-release-unsigned.apk
#Having trouble with using built apk
acoustic vapor
It shouldn't overwrite the file. If nothing got made there's something wrong. I don't remember the exact command for signing an apk, I should have it written down somewhere 🤔
Actually you're using jarsigner
You should be using apksigner
apksigner sign --ks my-release-key.jks --out my-app-release.apk my-app-unsigned-aligned.apk
acoustic vapor
Great! ^^
No problem and thanks, happy to help 🤗
acoustic vapor
Ah 😅 Well at least it's a step in the right direction that it installs. Hard to say why it doesn't work though without an error to go on
I think you should see some errors using ADB and logcat
acoustic vapor
God do I love ChatGPT sometimes, got a subscription to it yesterday 😄
The issue in this log is a java.lang.NoSuchMethodError error that occurred in the Android application with package name xyz.stormlightcandev.mobile_base64. Specifically, the error message is no non-static method "Lxyz/stormlightcandev/mobile_base64/RustWebView;.setAutoPlay(Z)V". This error suggests that the method setAutoPlay() is missing or not available in the class RustWebView in the application. This could be due to a missing dependency, an issue with the code, or a compatibility issue with the device.
That error is familiar
@slender nimbus isn't this the same issue that we saw the other day that someone had?
acoustic vapor
Downgrading is the only "solution" for now, right?
slender nimbus
Yeah looks like it
If I understand it correctly the fix landed in wry 0.28 but the next branch is still on 0.27
acoustic vapor
@supple arch looks like you'll have to downgrade all the way to 2.0.0-alpha.3 if you want to get rid of this issue
Alternatively, since you were able to develop with alpha.8, I'd probably recommend just continuing to develop your project and just hang tight for alpha.9 or alpha.10 or whenever we make a new release that uses wry 0.28