Game is in Unity 2018.03. Just uploaded a build fine on 3/29. Went to
upload a build today and I get "APK not signed" error. I've done the
exact same build process I normally do, and it appears to be signed just
fine using the same key I always use. ...
I'm not sure what changed on Oculus' side, but manually signing with
both v1 and v2 schemes seemed to resolve the error: apksigner sign -ks
"my.keystore" --v2-signing-enabled true --v1-signing-enabled true
latest.apk
Absolutely. Would be great for experimental ideas that don't make it
through the filter for Quest to still be able to get an audience without
needing those who might be interested to become a 'developer' with a
server-side authentication
I switched from internal to gradle and it started letting me upload
again. The real mystery is why did this suddenly started happening
despite no change in my build process or unity version?PS: I was getting
a weird MIPS architecture error when I swi...