Has anyone had any success obfuscating Xamarin.iOS apps using Obfuscar?
It looks like it's supported but the the documentation for configuring a project is almost non existent.
Related
I have been dealing with the same issue for a few days now. I'm unable to upload any app store connect files due to the libAgoraRTMWrapper file. To be clear, this entire app has been built through Unity using agora SDK. The reason for failure, according to XCode, is that the wrapper "doesn't have the correct file type for this location". Invalid Swift support.
This leads me to wonder if the libagoraRTMWrapper is even necessary. Yes, I would like to keep using RTM but not at the expense of several build failures.
As a sidenote, XCode does mention that the build is being made for iOS but the wrapper was built for iOS + iOS simulator. I don't remember ever specifying that but it could just be the way the SDK was initially imported.
this library is necessary for RTM to work. Do you have a custom build setting for the project? It is verified that the included SDK Demo works on iOS builds. Perhaps you can build that and compare the build setting to yours to find out what went wrong?
I've read the open source parse docs, and looked at the parse c# sdk. I also looked at back4app but their example is way out of date. I can't tell if I'm supposed to take the c# code from the official parse sdk and try to put it in Unity or am I supposed to build a dll first? There's not a lot of information that I can find.
The latest official release for this SDK was in 2016, as you can see here: https://github.com/parse-community/Parse-SDK-dotNET/releases/tag/1.7.0
There's a fork of Parse SDK that usually works fine, have you already seen it?
Here it is: https://github.com/fayezsalka/Parse-for-Unity-2018
I am a beginner in Xamarin forms. I have installed the plugin
https://github.com/jamesmontemagno/StoreReviewPlugin
I haven't found any usage documents on how to initialize/ how to do the setup for using the plugin when i looked on the web.
How can I display the prompt to the user using this plugin?
I just did a test and you do not need any additional steps to use this plugin.
Install this plugin through manage nuget packages and the in your project:
Use the namespace:
using Plugin.StoreReview;
Use the method:
CrossStoreReview.Current.OpenStoreListing("appid");
You need to test with a real device instead of a simulator.
The Store Review Nuget plugin has been updated to v3 recently thanks to the new (August 2020) Android native Play Core library so that it displays an In-App Review on both iOS & Android:
https://devblogs.microsoft.com/xamarin/android-in-app-reviews/
So now, initializing and setup is a lot easier and you don't need to pass the appid anywhere, it will be shown directly in the app
is there any experience using Crashlytics reporting system for xamarin.mac application? I tried to create binding library, I got an exception :
"Native linking failed with error code 1"
I'm not sure how binding library will work. any experience?
Here's some info that may be of use:
Fabric Kits available to use with Xamarin:
Answers Crashlytics Digits For Xamarin.Forms, Xamarin.Android and
Xamarin.iOS.
For iOS, you need to create a application with the same bundle id on
XCode as the one on your Xamarin app. Then, use the Fabric Mac app to
add your app and complete the Kits on-boarding process.
For Android, you need to create a application with the same package
name on android studio as the one on your Xamarin app. Then, use the
Fabric Mac app to add your app and complete the Kits on-boarding
process.
After that, you can follow the instructions on
https://www.fabric.io/kits to configure your projects.
For crashlytics on android, there is a hidden configuration, you need
to add/update the build id using a string resource
<string
name="com.crashlytics.android.build_id">e9e6beb9c4284289ac68b9ab76a9ee56</string>
Or else you'll get a crash on startup.
There is a Sample available on Samples folder.
On iOS, Crashlytics shouldn't be used with Answers. Crashlytics
includes Answers, so you should use either.
Code is available on https://github.com/drungrin/Fabric.Sdk.Xamarin
Nuget packages are also published:
https://www.nuget.org/packages/Fabric/
https://www.nuget.org/packages/Answers/
https://www.nuget.org/packages/Crashlytics/
https://www.nuget.org/packages/Digits/
Source: https://forums.xamarin.com/discussion/68256/fabric-crashlytics-answers-and-digits-for-xamarin-forms-xamarin-android-and-xamarin-ios
Mike from Fabric here.
At this time Fabric does not have support for Xamarin based projects. If that changes, I'll update my answer!
a more detailed instruction following the same answer as #CMash answer could be found here
I am doing a project for multiple platforms where I have followed best practices and created a core project to contain all the code that is the same on all platforms.
To do the network communication I would like to use HttpClient which seems to be the recommended approach for communicating with web services going forward.
I am NOT doing a PCL but just a standard C# library to contain the core project. However it seems that there is no common implementation of HttpClient but only platform specific ones. I cannot reference and use it in my core but only in my Android and iOS projects.
I would very much prefer to have all networking code in my core project and as I see it there are two options - neither of which I like.
Make a common interface that I can use in the core project that is implemented as a wrapper on both Android and iOS.
Use another technology that is supported in the core project - I am thinking webclient or the like.
What is the recommended approach and why hasn't Xamarin made HttpClient available as a common library?
Hope someone can help,
Thanks
I recommend checking out ModernHttpClient https://github.com/paulcbetts/modernhttpclient
It is a cross-platform networking library for iOS and Android. From the project:
This library brings the latest platform-specific networking libraries
to Xamarin applications via a custom HttpClient handler. Write your
app using System.Net.Http, but drop this library in and it will go
drastically faster.
You should be able to use System.Net.Http in your core library just fine, I've done it recently.
Make sure your core library is a .Net 4.5 project. There is a setting in project options for selecting the .Net version. After checking this, all you should have to do is reference System.Net.Http.dll.
If that doesn't solve your issue, are you on Windows or Mac(Xamarin Studio)?
I'm afraid you can't use HttpClient on Mono at the moment due to licensing restrictions. There is a UserVoice suggestion that you can vote on if you like.