I'm using apache cord for my application. The problem is this: If I'm building an application with a command Cordova build android (without --release), then everything connects successfully to the server. But if I collect applications for release, I can not connect to the server.
The application was published in Google Play. The assembly was successful. Maybe it's something to do with Google?
What can be the difference between the behavior of debug and relay applications?
cordova 8.0.0;
android-targetSdkVersion 23;
ok request
You almost certainly have a different signing key for your release application, and need to add the signing key for your release application as authorized to your server.
Related
Problem
We have an app on the Play Store. After signing in, or when the app opens, we make an API request to our server to pull the current account's profile information.
We've had an issue where this request isn't being performed.
What We've Done So Far
Running the app on a device with expo-cli, we traced the issue to an issue with certificates; we were missing the certificate chain.
We updated the configuration, and confirmed the fix when running the app via expo-cli on a device.
However, the app downloaded from the Play Store is still failing at this point in the app. The code we're running through expo-cli is what we built and published to the Play Store.
After routing requests on the the device through a local proxy, we can see that this request isn't being performed, which is what we saw running the app via expo-cli when the SSL handshake was failing. We think it's somehow the same problem or a different issue trusting the server's certificate.
When connecting to the server through a browser on the device, there are no issues with the certificate.
Questions
Any missing information I should include?
Is there configuration for the app that might be affecting our requests?
Is there a way to debug network requests other than a proxy?
Is it possible with eas or expo-cli to build an apk with debuggable true?
Thanks for reading.
When you want to test your android ionic app and point it to a test server (and you want others to be able to test it as well), what's the best practice approach for this?
Can you have the app check if it's running as a test release, and if so, use the test server? Or is there some better way to do this?
EDIT: I would like to publish the app to the Google Play store, and if it's a test release, have the app use the test server, but if it's a production release, then the app would use the production server.
If I understood you correctly, you can use angular environment (baseUrl) like in usual angular web-app, and just add --prod or --test as a parameter.
for example:
ionic capacitor copy android --prod
I've got a Cordova / Ionic App developed by an external group that we're trying to do some QA testing on. To build out these tests we're attempting to intercept the application with a proxy so we can monitor what API calls the application is making. However, every time we configure the Android or iOS device to use a proxy; the HTTP calls in the application error out.
We have already imported the Certificate Authority of our proxy into the device as a trusted Certificate Authority, and this is confirmed working in the native browser (We can go to SSL sites without any errors/prompts).
The development team is telling us that they haven't done any certificate pinning, or anything "extra" besides what is built into the framework. They are confused as to why our proxying isn't working.
Can anyone tell me what default "platform features" that is preventing our proxying from working, and what we need to tell the development group to give us a build that will allow us to do what we need to do?
Just to be clear, all we have available to us directly is the APK and the IPA file. We do not have the full source-code. We can request the source-code be changed with a new build for us to use; but we cannot just run the Cordova app.
I'm working in an application developed with phonegap 3.3.0 and i'm using build.phonegap.com to build the apk's. This app works with a REST server, so it uses POSTs and GETs. This app works fine in debug mode, i mean, without sign the application with the builder. But if i setup the keystore to sign my android app and then i install the "app-release.apk", the installation works fine, the start of the application works fine, but all GETs and POSTs return always 404.
For the record, i've checked the access whitelist in config.xml.
Any idea?
Are you sure you have applied the self-signed certificate? Because debug: true is being set only when the app is built with a debug certificate.
I am in the final stages of getting my first android app ready to go out to the play store. To test my final signed release build I emailed the APK to my phone and installed as an 'Unknown App'.
Everything looks to be working fine except my GCM push registration process. I don't seem to be getting a response from google when I try register. If I deploy this same build from my IDE to the phone everything works fine, no code changes at all..
Are their any restrictions on GCM registration? Does the app have to be deployed from the Play store for this process to work?
Any guidance would be great!