I want to use Crittercism in iOS app built by xamarin, but the app will crash after enable it. I have found the solution at How to create crashlytics binding for Xamarin.iOS? and add the codes suggested but the app still crash. The version of Crittercism is 4.3.0 and xamarin is 4.2.2. Does anyone successfully make it working under that environment?
Thanks!
This is Rob, one of the co-founders of Crittercism. We actually just released an officially supported Xamarin Plugin! It handles interactions with the Mono runtime pretty nicely - for example, we purposely don't override fatal signals like SIGSEGVs which the Mono runtime should handle and send us better stacktraces. You can download it here:
http://components.xamarin.com/view/crittercism
Related
when I submit my app to testflight I get the following warning.
(I am using the latest version of Xamarin forms and Xamarin Essentials)
App Store Connect
Dear Developer,
We identified one or more issues with a recent delivery for your app, "XXXXXXXX" 18.8.0 (18.8.0.89). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage - App updates that use UIWebView will no longer be accepted as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).
After you’ve corrected the issues, you can upload a new binary to App Store Connect.
Best regards,
Please read the document about UIWebView Deprecation and App Store Rejection (ITMS-90809) and make sure your project has meet all the requirement:
A preview version of the linker is available to fix this issue. To enable the preview, you will need to supply an additional argument --optimize=experimental-xforms-product-type to the linker.
The prerequisites for this to work are:
Xamarin.Forms 4.5 or higher. Xamarin.Forms 4.6, or higher, is
required if your app uses Material Visual.
Xamarin.iOS 13.10.0.17 or higher. Check your Xamarin.iOS version in
Visual Studio. This version of Xamarin.iOS is included with Visual
Studio for Mac 8.4.1 and Visual Studio 16.4.3.
Remove references to UIWebView. Your code should not have any
references to UIWebView or any classes that make use of UIWebView.
Recently my app was getting crashed on IOS8 because i have used an API which is only available for IOS 9 and above. I am wondering is there anyway to check the whole project and find out if I am using any API which is not available for the current development target. Something like the warnings for the deprecated APIs. Thanks.
In order to tell the compiler you want to support an earlier OS, you need to set the SDK to that earlier OS's SDK. If you set the SDK to iOS 8, then any time you use functionality from a later OS, you should get a compiler error.
I'm trying to use crittercism to know the crash in my app, the problem is that when crittercism have a crash report to send of web service, my app crash. so I can not open the app again.
The only possible to open the app is, run again the app with xcode, put a break point unit the line [Crittercism enableWithAppID:#"XXXXXXXXXXXXXXXXX"]; and run line per line.
In this moment crittercism send the report and I can run my app normally.
What can I do to resolve this ?
To additional information I am using, ios 8.3 in ipod 5g and xcode 6.3
Thanks.
One of the founders of Crittercism here. Which version of the Crittercism SDK are you using? There was a small bug in v5.1.5 of the iOS SDK that we're fixing now which may be causing that issue. If you downgrade to v5.1.3, it should work:
http://docs.crittercism.com/downloads/downloads.html
Take care
Rob
My company integrates Unity games into our native iOS app. Basically our iOS app would run the Unity code when a user decides to launch any of the games.
With the past 32 bit of Unity and native iOS code, we were taking Unity generated Xcode files, and compiling it into a static lib for the native iOS app to use. Whenever the user chooses to launch any of the games, UnityAppController would be loaded, and ran. This worked well for us.
But with the latest 64 bit builds, the same approach would give us a runtime error on app start - specifically when "main.mm" is executed, the app would crash at the "InitializeScriptingBackend()" call in "main.mm". Please see attached screenshot for sample stack trace.
Same issue happens regardless if we are running in debug or release scheme.
We are currently using Unity version 4.6.3p3 for generating the games for iOS, and using Xcode 6.2 for compiling the Unity code to static lib.
Does anyone have any idea why the crash is happening, and how we might get around it? Thanks!
Another discussion is happening on official Unity forum: http://forum.unity3d.com/threads/runtime-issue-with-64bit-unity-game-integration-into-ios-native-app.316796/
After I updated Facebook iOS SDK from 3.2 to 3.5 I'm getting this error when running my app in a device with iOS older than 5 (eg 4.3.5).
dyld: Symbol not found: _OBJC_CLASS_$_NSJSONSerialization
...
Expected in: /System/Library/Frameworks/Foundation.framework/Foundation
I can avoid this crash if I set Foundation framework as Optional, but I don't think this is the best option.
Is there another way to make Facebook SDK works in devices with iOS previous to version 5?
From Facebook iOS SDK changelog v3.5:
http://developers.facebook.com/ios/change-log-3.x/
Removes support for iOS 4.* Facebook 6.0 dropped support for iOS 4.x. To stay in sync, the Facebook SDK is also does not support iOS 4.x.
So, if you update to Facebook SDK 3.5 you lose support for iOS 4.x
That class was not available until ios5 - look at the class reference in the Xcode documentation window. What you need to do is grab JSONKit, an open source class, and use it. Usage is mostly the same. You will need to build this class into your app then test dynamically if the apple class exists, then use the appropriate class, or just always use the open source class.
Note that JSONKit is not ARCified, so you need to set the appropriate compile flag for it if the rest of your app is ARC.
Edit: so you may be able to get clever and write your own stub that bridges calls to JSONKit in older releases. Conceptually you should be able to make this work, but my fear would be that if the FB code was developed for ios5 then there may be other Api problems lurking in the code too - and you old spend a lot of time continually trying to find and fix them.