So i recently made a build (.apk) for my app and the authentication works fine. But once I login the app crashes with error:
appName[65858]: assertion failed: 20C69 18C61: libxpc.dylib + 50260 [056A9371-1C2C-385B-BB06-F099DE20E73A]: 0x7d
My app runs fine on the simulator, and I can't make anything out of this error log.
Thank you very much for your help and please let me know if you need more information.
As you said, it is difficult to figure out what's happening just from that error. You should definitely try to debug more. You can always run a release build on your simulator using:
npx react-native run-android --variant=release
Maybe this way you will get more insights.
Because you mentioned something about authentication I assume you are making some HTTP calls. Possible issues:
The API URL. Maybe you forgot to change some localhost endpoint. Make sure the server is accessible and double-check everything related to that.
You are making API calls over HTTPS. Depending on your config, you may be allowed to make a network request over HTTP in Development, but on a Production build, you definitely need HTTPS.
Related
I've been struggling for the past few days trying to resolve the issue with all my axios requests. No matter what I change, I keep getting the error:
[Error: Network Error]
When this error happens, it closes the application into the background of the phone but doesn't crash. There is not other error logs or warnings so it's I'm finding it hard to debug the issue.
This is not being sent to localhost, this is sent a public domain as I know there are people having issues with localhost and having to switch to use IP address. However it's happening when I'm using public domain.
Has anyone come across this with their expo build on android before?
Update:
The APIs work in postman, so it's only an issue when sending requests via the expo application.
Update Fixed:
Finally found the issue flagging:
canceled due to java.lang.NoSuchMethodError: No virtual method toString(Z)Ljava/lang/String; in class Lokhttp3/Cookie;
I had to had the following to build.gradle
implementation 'com.squareup.okhttp3:okhttp:4.7.2'
implementation 'com.squareup.okhttp3:logging-interceptor:4.4.1'
implementation 'com.squareup.okhttp3:okhttp-urlconnection:4.4.1'
Android dont accept HTTP protocol Api so keep sure you are using a HTTPS protocol Api
So I have started work in an app built with jhipster. I have made changes to one microservice and want to run only that on my local machine. But I am not able as it gives me a 401 error. Frustrated I simply deleted the securityConfig.java file in app/config and now it keeps hitting me with a login page.
please help.
I'm weblogic newbie, trying to abandon it ASAP, but that's not possible for now, so I have to resolve this. Maybe following is completely normal and trivial. I don't know. Please advice.
I had working weblogic 12.1.3 on 2 PCs for months. But suddenly, I cannot log into admin console on neither of them. I enter username/pass from password store, and it's not accepted. While at the same time intellij idea successfully logs in and deploys app using same pass. OK, fair enough, we reset pass, using:
https://oracle-base.com/articles/11g/reset-the-adminserver-password-in-weblogic-11g-and-12c
and update password in intellij settings. Good. Intellij idea is in again, I cannot login. Nothing in logs, neither application, nor server logs.
I cannot login regardless if I start weblogic via intellij run configuration of from bash.
OK, lets try reinstall weblogic. No change.
Weblogic is up and running, app deployed to it, and is responsive. When accessing console URL, it gets printed, that app is being deployed, but I still cannot access it. Cleared caches/cooking etc. nothing. No logs, no error response. Nothing.
Responses to "failed"(?) login on urls j_security_check, console and console/ are http status 302 (moved temporarily). Not sure if it's ok or not, well say I'd expect 401/403, but maybe 302 is valid weblogic response for denied authentication. I don't know.
Any idea?
What you can do is to check web storage and try to clear it. But the most clear way is to use different browser. Or use your current browser in private mode. Also in firefox you can create different profile and use it for this specific purposo.
The hybrid android app made from mobilefirst cli 7.1 is not getting the authorization token from the mobilefirst server in our UAT environment which has webseal junction, so the subsequent adapters calls are failing as 401 unauthorized is returned for these calls, what makes this interesting is that ios app which is made from the same client side hybrid code works well with the same UAT environment with webseal.
one more interesting fact is that same android app works fine when pointed to SIT environment where there is no webseal .
So i am trying to understand what triggers the client ( WLHybridRequestSender)to send out the" /authorization/v1/token " call , and is there a chance that the webseal is filtering any response to a preceding call "token" call thats is breaking the client side code? if so where and what should i look for to resolve this issue?
Any advise or help is much appreciated !
Thanks
This issue was already fixed, you can find more details about it, here.
You should update your cordova-plugin-mfp 7.1.0 plugin using mobilefirst cli:
mfp cordova plugin update
This updates the Cordova assets for each plug-in that is installed in the app.
Please notice that you must execute the command in Cordova project folder.
You can read more about mobilefirst cli in this tutorial.
I have been seeing this error when trying to login to my app.
It is using the mfp auth framework
any explanation of what this is would be very helpfull
I see this in the simulator, I don't see this on the device, but wl.connect() always fails in the device
This was due to direct update, anytime a direct update happens i get this error, then i have to shut down the app and restart it
I had the same issue in simulator, deleting and reinstalling the app fixed this.