react native intercom couldn't load your conversation - ios

Intercom message couldn't open sometimes on production mode.(iOS)
It works fine in debug mode.
There is no error or warning on console.
Did anyone face this issue?

I had the same issue.
You need to check if your API key is setup on Settings > Installation > iOS
https://developers.intercom.com/installing-intercom/docs/ios-installation#section-step-3-initialize-intercom

Related

Airwatch SDK iOS - We were unable to retrieve the configuration information

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?

ionic4-iOS white screen in iOS Simulator

I'm using XCode11 and ionic4. cordova version ios#5.0.0
project builds successfully using ionic cordova build ios
also successfull build in xcode
but when running on simulator, it end up showing white screen and nothing happens next. here is the console output showing the issues:
Log1
Log2
stuck on this for 4 days. checked so many suggestions on ionic blogs and nothing worked so far. I regret using ionic because its very buggy/unstable... please help
ISSUES:
-Failed to load webpage with error: the operation couldnt be completed(NSURLErrorDomain error -999)
-NSURL Connection finished with error -code -1100
-ERROR: HTTP Request(OSRequestRegisterUser) must contain an app_id parameter
-ERROR: Encountered error during push registration with OneSignal
in addition to the above errors, the iOS simulator hangs on "White Screen", the application does not load and nothing happens next.
Try this:
On your xcode, navigate to your plugin folder, locate a file named OneSignalPush.m
Inside, locate the initOneSignalObject,
add this: appId = "your-app-id-here";
right after this code:
[OneSignal setValue:#"Cordova" forKey:#"mSDKType"];
That did the trick for me.

I am facing an issue with phone auth. The phone auth is working fine in development, but throwing an error when in test flight build

When I am clicking for generating OTP with signinwithphonenumber() method. Firebase returns "Error: An internal error has occurred." this error in some iOS devices. While in development it is working fine. But test flight build returns this error in some devices and working fine with other device. I have done coding in react-native.Can anyone please help me resolving this issue? It would be a great help.
Thank you.

IOS app stuck in splash screen on IOS version 10.2.1 with no error

My iOS app was perfectly working till yesterday. My QA was testing and there was no bug at all. But when I tried to install from Xcode to my iPhone 6 somehow it got stuck in splash screen and debugger shows absolutely no error. I googled a lot but no luck. I even tried to run previous version by switching my current branch but no luck.
This is what my debugger look like:
2018-02-07 12:49:56.982145 Marham[547:85300] 4.8.1 - [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40009000 started
2018-02-07 12:49:56.982649 Marham[547:85300] 4.8.1 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see [some-Link])
2018-02-07 12:49:56.983029 Marham[547:85300] 4.8.1 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
[some-Link]to ensure proper integration.
(lldb)
and here is the surprising thing for me that, app runs without any issue on simulator but got stuck only on real device.
Do you still have this issue ?
Because I had a similar one and that was because a local storage variable was blocking the execution of the first view on the phone (the simulator was working fine).
So I advise you to put your phone on debut mode and make a breakpoint on the main function in the App Delegate.
This way, you should be able to se if there's an async function waiting for nothing.

iOS app cannot connect to MobileFirst server

i created an hybrid application that should connect to the MFP and consume data.
When i try to connect to the Desktop Browser Application everything is fine and the app works. Same behaviour when i try the Mobile Web Application. BUT when i try to connect with the mobile native iOS application i could not connect and receive the following error (in the console):
2015-11-12 17:22:15.031 APPXYZ[6072:3089110] [FATAL] [NONE] Uncaught Exception: TypeError: WLJSX.Ajax.WLRequest.setConnected is not a function. (In 'WLJSX.Ajax.WLRequest.setConnected(false)', 'WLJSX.Ajax.WLRequest.setConnected' is undefined) at (compiled_code):3871
My specs:
MFP version 7.1.0.00.20151107-1653
Xcode 7.1.1
iOS deploy target 8.0
Transport security protocol is deactivated (Allow Arbitrary Loads -> YES)
I cannot confirm this claim.
Using the following, I create a blank new Hybrid app with the iPhone environment, that calls the WL.Client.connect method in wlCommonInit() and displays an alert with "success" or "failure" accordingly. I got "success". No errors in the Xcode Console.
Xcode 7.1.1
IBM MobileFirst Platform Studio 7.1.0.00-20151107-1647
If you are doing something different in your project, do let us know...
The solution of my problem was that i change the init calling sequence of my app. I called the wl specific functions to early. After changing the sequence my app runs perfectly.....
thx 4 help :)

Resources