We are facing issue with "iOS Push Notification" functionality with Mobile First 7.0.
We have downloaded push notification sample app from
Sample App. As MF 7.0 doesn't have any sample app. So we used sample app of MF 6.3.
After installation we have tried to "subscribe" through iOS device. Its throwing below error and app is crashing.
[ERROR ] FWLSE0020E: Ajax request exception: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. [project PushNotifications][ERROR ] FWLSE0117E: Error code: 1, error description: INTERNAL_ERROR, error message: FWLSE0069E: An internal error occurred during gadget request [project PushNotifications]The transaction has been rolled back. See the nested exceptions for details on the errors that occurred., User Identity {wl_directUpdateRealm=(name:null, loginModule:WLDirectUpdateNullLoginModule), SubscribeServlet=null, wl_authenticityRealm=null, wl_remoteDisableRealm=(name:null, loginModule:WLRemoteDisableNullLoginModule), SampleAppRealm=null, wl_antiXSRFRealm=(name:mibphsqb0hb1bfcko7t0nfstts, loginModule:WLAntiXSRFLoginModule), PushAppRealm=(name:Test1, loginModule:PushAppLoginModule), wl_deviceAutoProvisioningRealm=null, wl_deviceNoProvisioningRealm=(name:89E62244-B169-4C8E-BB83-BD7F6868310E, loginModule:WLDeviceNoProvisioningLoginModule), myserver=(name:b71e8870-df42-424a-bc38-924c645d621e, loginModule:WeakDummy), wl_anonymousUserRealm=(name:b71e8870-df42-424a-bc38-924c645d621e, loginModule:WeakDummy)}. [project PushNotifications]
com.worklight.common.log.filters.ErrorFilte
Why are you saying MFP 7.0 doesn't have any sample? it is linked to in the tutorials for MFP 7.0, here: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/notifications/push-notifications-hybrid-applications/event-source-based-notifications/
So first try to the appropriate sample.
Additionally the error log does not reveal anything... provide logs from Xcode.
As for the crash - make sure you are using the latest MFPF 7.0 iFix from IBM Fix Central as an iOS push-related fix was delivered some time ago. You may be using a version affected by the bug.
Related
Using the Airwatch SDK v21.4 on iOS an error is shown:
"We were unable to retrieve the configuration information. Press
continue to try again"
Using Airwatch SDK 20.9 worked fine, but after upgrading to version (21.0 thru 21.4) on iOS the SDK is displaying the error.
The message text can be found in an AWSDK.framework file Localizable.strings within the entry RetryToFetchConfigurationInformation
I can do a fresh install from the HUB app just fine.
After launching the app the UI is not displayed until a successful response from controllerDidFinishInitialCheck.
My controllerDidFinishInitialCheck method does not contain any errors.
After receiving a valid controllerDidFinishInitialCheck result the UI is displayed, followed by a popup alert message with the error.
Advice / Suggestions / How can I isolate this issue? It may be a timeout issue?
I am currently having a problem with logging into firebase on my iOS app, I recently got a new laptop and decided I would migrate from swift 3 to 4 on there, however I discovered a problem, before I hit the convert everything to swift 4 and got tons of errors, I launched the app still running on Swift 3, but I couldnt seem to log in, I am getting the error showed below.
I then switched back to to my old macbook air that is still got the orignal app and old version of xcode running and tried logging in there as I usually would. However, still getting this error showed below. There is not much context shown as I just get "null" in the localised description? Has anyone been faced with this?
This is just standard email authentication with Firebase
error Domain=FIRAuthErrorDomain Code=17999 "An internal error has occurred, print and inspect the error details for more information." UserInfo={NSUnderlyingError=0x6000008466c0 {Error Domain=FIRAuthInternalErrorDomain Code=4 "(null)"
I am fairly certain that the answer to this question is "No", but I am asking anyway. My evidence that Beta by Crashlytics does not support iOS's on-demand-resources is an app build that works fine when downloaded from TestFlight, but throws the following iOS error when downloaded from Beta:
Error Domain = NSCocoaErrorDomain Code = 4994 “The requested
application data doesn’t exist.” UserInfo = {
NSLocalizedFailureReason = Request code not be completed. Invalid tag in set ‘{(cardImage, cardAudio)}.’ }
I have received confirmation from Fabric that they currently "don't support apps via Beta using on-demand resources."
I'm trying to submit my app the the App Store using Xcode 5.1.1, but I keep getting this error message during validation:
an error occurred while processing the json request
That's it. No extra information. On one of my tries I also got an error saying that the connection was lost. I tried restarting Xcode as someone suggested in another post, but it didn't help. Is this an Apple server issue?
90% of the time it is, yes. Don't worry and resubmit it a couple of hours later.
Or use Application Loader.
Anyone encountered this already?. I downloaded the sample code for IOS from github. I replaced the app id with my own, that i got after whitelisting my device. I ran the app and selected the device and media to cast. Soon after I hit the cast button, I am getting the following error....
Failed to start application (com.google.GCKFramework.GCKApplicationSessionError); caused by: entity not found (com.google.GCKFramework.GCKNetworkRequestError).
Found solution for this one. Once I enabled the Chromecast to send it's serial number to Google, the error went away (for future reference). It can be done in settings.
Source: https://github.com/googlecast/cast-ios-demo-player/issues/5