Created a basic HTML, CSS, Javascript app using phonegap desktop developer app, phonegap mobile developer app, uploaded this to github public repo.
After creating a phonegap-build account , I created the android apk build using phonegap-build referring the source from github public repo url.
Installation of apk file in android device went fine, but when I try to open the app, it is stuck at this error "Initializing…. Please wait". This is stuck at this stage for long time and can't get past it.
Found that , I had enabled 'hydration' while creating the apk using phonegap-build.
After disabling the hydration, and doing a rebuild and re-generated the apk, installed it on the device, now it is good.
Related
I have already published my app on the playstore with keytore as .apk I am used to. But because of google notice that publishing App as APK will be obsolete in few months to come.
So, in a new upgrade of my app, I wish to upload it as app bundle. So while generating signed App bundle, with my app's keytore, I discovered that it generated the app bundle as (app-release.aab) and exported another key as private_key.pepk So when i revisited playstore console to upload the signed app bundle, I didn't see where to upload private_key.pepk.
So, I became worried. Not knowing what to do. I don't want to make a costly mistake. That is why I'm here for you to give me step by step method on how to continue from where I stopped.
Thanks for helping me..
EDIT:
I clicked create new release and then I clicked on opt in but didn't know which option to choose and proceed
Opt in to Play App Signing
Export and upload a key from Android Studio
Export and upload a key from Java keystore
Export and upload a key (not using Java Keystore)
I have Flutter Firebase auth configured and it is working perfectly with Android. But with ios, I cannot seem to get it to work.
Am using Xcode and Flutter on MacOS deploying to a physical iphone()14.4) and I have followed the instructions:
Added googleservice-info.plist into project via Xcode.
Under Signing and capabilities in Xcode, Provisioning profile, Team , Bundle identifier, Signing certificate(Apple Development certificate) configured with no errors. Push Notifications(Release) also enabled.
In developer.apple.com, under Identities->myapp, I have enabled Push Notifications. I have also created development and production SSL certs inside Push Notifications. Also created key for Apple Push Notifications service (APNs).
In my Firebase project, I have added iOS apps and all the fields are populated. Under Cloud Messaging, in iOS apps, I have uploaded the APN key and both development and Production certs I got from Apple Developer.
I run 'flutter run --release' (I am using a physical iphone(14.4)) because debug mode is not allowed on 14.4. App installs successfully. I am able to navigate pages and even register email/pw with Firebase. But when I do a Firebase phone auth (verifyPhoneNumber), I keep getting an error as indicated by a snackbar error I coded in. Problem is that I cannot get the specific error from the logs since I have deployed using release and flutter logs remain blank.
I don't know what else to do. Please help.
Figured it out. Problem was with URL Types under Info of target Runner. Had to add URL Scheme. For those who has this problem, refer to the below.
https://firebase.google.com/docs/auth/ios/phone-auth
iOS uses captcha with Firebase.
I have developed an app and integrated with Admob using cordova-admob-free. It works fine when the release apk is installed to any device (test or not). It also works when the app is installed to a test device from play store.
However, in any other device that installed the app from the Play Store, ads are not shown and LOAD_FAIL event fires with error code: 3 and reason: No fill.
My admob profile is complete. (I have an older app with working ads)
I have the <variable name="PLAY_SERVICES_VERSION" value="11.0.0" /> dependency in the config.xml file. (I also tried the version 17.0.0)
I created app-ads.txt in my developer website
I tried to create new ad units and use them
I didn't try to remove the app from the store and create another one as it takes too long to be confirmed.
I couldn't get any reply from the Admob support or github repo. I appreciate any help. Thanks.
Since the ads was working when installed from apk, I thought the case is different from newly published apps. However, it just begin to work after 8-10 days from publication. As the other "no fill" error cases, the solution was just waiting.
enter image description here
I built ipa file with react native expo and i attempted testing on devices.
I connected my own iphone to mac and used xcode + button for upload.
But i got a this message that "Unable to install (appname)" . Can I test the app(that built by expo) on the my own device?? I already registered apple developer accounts at yesterday.
According to a thread on developer.apple.com, this issue got resolved after the iOS version 13.4. Please review your developer account and it's license, as it usually happen with non-paid developer account.
Quick way to testing your app, upload your ipa on diawi.com and with QR Scan or Share link, you can download and install app on your device.
I have a strange problem with the creation of ipa.
I have a web-app with an old ipa.
Now, I have the latest version of Xcode (7), I've tried to do a new ipa with the same files (of that web-app) and it doesn't work.
When I create the new ipa, I select "create for ad hoc deployment" and I don't send it immediately to app store.
I noticed that the new ipa is smaller than the old ipa.
I can install the web-app on my iphone and the app starts, but the jquery-mobile seems doesn't work.
Also, it seems that it can't do external calls (for example to a website).
If I install the old ipa, it works all.
I program the web-app with phonegap not with xcode.
I use xcode only to create the ipa.
Anyone know if there are problems with new version of Xcode?
I've tried the new ipa with iphone 6 and iphone 6 plus.
With apk for android works perfectly.
Thank you so much.
I've found the solution.
The external links were the problem.
In the new Xcode it's necessary to add a code in the config.xml that contain the external links that the web-app uses.