Closed seadramdesenv closed 1 year ago
Your ADB output doesn't really show anything relevant (it shows beginning of system boot but sometime before the application initializes Cordova).
However, problems inside the webview generally indicates a logical problem in the application itself. That is Cordova is a packaging tool that loads up web assets into a webview, but from there Cordova is fairly hands off.
I would try using Chrome's web inspector, which may give us further insights on your issue via the JavaScript console. Cordova debug builds have web inspector access enabled, so by using either the simulator or a physical device via USB, you can remotely debug the webview via the Chrome web developer tools.
I wasn't able to debug correctly, but the way it went, it's debugging now and I found the method that causes the error
Before updating android cordova to 11 I used targetsdk as 30 and changing it to 31 stops my authentication working
I imagine that something changed in question when using sdk 31 but debugging I still couldn't identify it, but since it no longer involves cordova I appreciate the help
Thank you even more if you have any suggestions for analysis
If you want I can send you the source. thanks
HTTP Status 400 Bad Request is a server error. Assuming you're following specs/guidelines, it generally something used on the server to indicate that the client sent something to the server that wasn't expected, or it didn't follow the API.
If your server returns error data, it would be in the response. Otherwise you'll need to look at your server logs to gain further insight, assuming that your server application logs out error details to learn why it might be returning a 400 instead of the expected response.
Nothing here indicates an issue with Cordova itself, so I'll be closing this issue. Should you isolate your issue further and find an actual bug within Cordova, please open a new issue with the newfound information.
Recently our team had to upgrade the target sdk of our Android Cordova generated app to 31 and cordova itself to 11, from, respectively 30 and 10, due to Playstore changing it's policies and forcing apks generated to be of sdk 31 or higher, but we ran into a problem specifically with our login button in the first page where it apparently doesnt throw any errors and just doesnt work. Very little changes were made to the code from the version prior to it and it works fine in the web environment but not in the App using WebView, the most we get is the following message :
ADB LOG
Some of the attempts
Tried using Webview with a basic Flutter app and it worked fine, also tested it in the regular web environment built with Java and Angular and also worked without issues.
My AndroidManifest
My Config.xml