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.
Related
I have developed an Android app using react native.
When I run on simulator its fine, and also when I debug via USB on real device its fine.
However when I publish to Google Play store and download the app as a regular customer it sometimes crashes.
Are there any logs somewhere that I can refer to in order to identify what the issue is? Or perhaps there is something I can add to code to help identify where/why issue is occuring.
You can use log errors to do so, record the activity of user. When the app crashes, your app can ask the user to send the bug report.
Using that bug report you can understand why your app crashes.
You could also use tools like Sentry or Firebase Crashlytics with an Error Boundary
wrapping your app to report errors, allowing you to have a better understanding of the production errors by displaying the full error stack trace and a lot more.
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.
Maximo Anywhere working fine in simulator, not able to login from iPad device (any device).
Response is NULL from adapter - Login call with an error (Security Realm). Attached the logs for the same. Kindly help. I checked wlclient.properties also but i not able to login. at same time i can able to login worklight simulator.
Thanks advance
above that issues i resolved. Below that property resolved my issues,
NSAppTransportSecurity
NSAllowsArbitraryLoads
And i following this links are very helpful us.
https://developer.ibm.com/mobilefirstplatform/2015/09/09/ats-and-bitcode-in-ios9/
https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html
I am updating an app for iOS 6 Address Book authorization and have hit a problem in testing. The simulator always returns that authorization is granted. This means I do not see the dialog popup requesting permission and can therefore not test that code path. Ok, use a device instead... The problem there is the OS appears to remember my answer so only asks once. Deleting the app does not help. On reinstalling it has retained the permission setting from before, so again no popup.
Resetting the simulator does not help and if you go into the Privacy settings on the simulator no apps are listed as requesting permission to the Address Book.
The only option I have is use another iOS device that has never had our app installed on for each test. This cannot be how you are supposed to test this. Any ideas anyone?
Thanks
Found it. From the device, Settings->General->Reset->Reset Location & Privacy. So you have to do that for each test
I'm trying to get device token in iPad for remote push notifications;
registerForRemoteNotificationTypes is called okay, no error, but didRegisterForRemoteNotificationsWithDeviceToken also not been called;
Application is appear in Settings/Notification;
What's I doing wrong?
iPhone is registering successfully.
Thank you
PS: iPad 1, iOs 5.1
In this case, if the code works on iPhone that code should work on iPad as well. Coz the os is same. Anyway if your code is not working on iPad try to remove provisioning profile from the iPad and reinstall the correct one. Sometime the old provisioning profile remains. And don't forget to check the code signing on target as well.
check that you are registering correctly for Push Notifications, including verifying your provisioning profile for "aps-environment" key and the code signing of the .app.
also you can debug Push Notification status messages in the console (you will need to install PersistentConnectionLogging.mobileconfig provisioning profile on your device and reboot it. check out this link under "Observing Push Status Messages").
There is an important thing to know with the provisioning profile. You should ensure to create the certificate first (the one used for the notifications), and then recreate the provisioning profiles, so that they know about the notifications. So you're sure it's not a provisioning profile issue.
Well, problem was solved in production sign and provisioning, but not in development. When I archive application for device and load it through iTunes, push notifications is working. Very strange behaviour.
I know it's a late answer, but it may help others. I had the same issue as the OP. After you click ok on the notification popup, it disappears but none of the method gets called to get the device token. Then I checked the internet connection when testing push notifications and I realized I had no connection. After re-connecting, it began working fine.