i.e this works: meteor run android-device --mobile-server=https://x.y
this does not work–>
As soon as I create a signed apk from either mup or from meteor build, the signed apk stops working, whereas the unsigned apk worked before. The app opens on the phone, shows the index.html but when I click signin on the accounts-ui nothing happens.
The signed apk uploads to the play store, but the downloaded apk shows index.html content and then nothing. I click the sign in button, nothing happens.
I have seen several people raising this issue and have tried all of them, still it doesn’t work.
Things I tried:
change --server, mobile-server flags in several ways
check ssl certificate intermediaries
change CN in certificate
change root_url, DDP url, mobile_root_url, mobile ddp url
Nothing works
Here is the logcat:
02-08 13:13:27.683 3698 9958 E BoostFramework: Exception java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])’ on a null object reference
Please help. Now my app is ready for publishing, I have been cracking my head over this for a few days.
I am wondering why you are mentioning mupx and meteor build here. Both tools have nothing to do with app signing. Signing is a completely separate process that comes after building your app with meteor build. Are you sure you followed all steps to build an app and sign it?
Here’s the steps required:
meteor build to a directory
Sign the app using jarsigner
Zipalign the app using zipalign
If you’re using Crosswalk, each of the steps would have to be done for two APKs, one for armv7 and one for x86.
Also make sure you have set the right access rules in mobile-config.js. Otherwise, your app won’t be able to communicate with your server.
BTW: Have you tried to debug your app using Chrome’s remote debugging feature? This should show you any connection problems.
Both mup and meteor build can sign the apk if you put the release-signing.properties file in the platforms\android directory.
Rest of your very helpful suggestions I can report that they are taken care of, while the problem still persists!
Not sure what this chrome remote debugging feature is. Can you pls elaborate? Like I mentioned, my app works prefectly in debug mode, only when it is signed it simply doesn’t.
And how do you start it on the server? Using node or using meteor? The latter is only meant for development environments. I am deploying to AWS via mupx and everything is working fine in this scenario. Still, the strange thing is that your app tries to connect 10.0.2.2:3000. This looks like a local development system.
Would you like to do a web session on this? You can contact me via Guzz, and I could show you how I set-up things. My Guru profile is: http://guzz.guru/waldgeist
But as the issue stated that it was fixed in 1.3, I thought this was irrelevant.