I have a game which is made with Unity, using both Facebook and Vungle SDKs. This works fine for me in the Android build.
However, when I port this to an iOS project and try to build it, I am getting link errors. Looking through the errors I can see that one of either Vungle or Facebook is always missing. Moreover when i first make the XCode project it has Vungle SDK included but not Facebook and, if I build again to XCode it will have Facebook but no Vungle SDK.
Any subsequent builds come with Facebook only. I have tried many times to rebuild the project. Now is there a way that i could merge these two projects if at all it is possible?
This is giving me the link errors. Can any one tell me whether i am doing something wrong.
The screenshots for the images can be downloaded from the links below:
Also, I can see that Facebook is replaced by a StoreKit framework. Did anyone come across this issue?
It sounds like both SDKs are rebuilding the Xcode framework search paths / linked frameworks from scratch.
You might be able to get around the issue by exporting the project with Facebook included, and then manually adding the Vungle SDK framework into the Xcode project (outlined at https://support.vungle.com/hc/en-us/articles/204430550-Get-Started-with-Vungle-iOS-SDK).
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 developed a small SwiftUI app that uses FMDB as a framework. I've done this with several other apps in the past and encountered no problem. With this one, I ran into the problem that though it would run on my test devices and the simulator, it failed App Store upload with a message that signing the FMDB framework failed (using "embed and sign" option; this is a problem for another question, for sure). After lots of frustrating research and unsuccessful trial-and-error attempts, I decide to remove the FMDB framework and bring in the FMDB source, so I could get it to the App Store.
That seemed to work, as I can upload the app to the App Store and run it on simulators, but when I run the app on a device, I get the message, "dyld: Library not loaded: #rpath/FMDB.framework/FMDB" and accompanying stuff. I can find no remaining reference to the FMDB framework, but obviously Xcode can. I've cleaned the build folder, deleted derived data, deleted the app from the devices for a fresh install, cursed and moaned, and tried multiple devices.
Any ideas where to look to remove references to the FMDB framework? Ideas on why this is happening?
To my understanding, Nativescript takes the javascript (or typescript) + nativescript code and creates project files for both android and ios in order to be able to run them as native apps. I also know that these files all seem to be located in the Resources directory. However when I try to run a simulator from the xcode project that is created, it fails.
I don't want to know how to fix the simulator failure, I just want to know if it's possible for a swift developer to take the xcode project created by Nativescript and continue developing as a regular native app.
If so, is this possible with the android project as well?
Please check this out
https://www.nativescript.org/blog/using-nativescript-in-an-existing-native-ios-android-applications
The two articles explain in detail how you can embed the NativeScript runtimes in native Objective-C and Android applications.
I have a solution with 4 projects 2 PCL's, a Droid Library and a droid App. When I reference the Droid Library from my Droid Application at compile I'm getting:
Error XA5211: Embedded wear app package name differs from handheld app package name.
In both Xamarin Studio and Visual Studio.
Thing is it's not a wear app package nor do I have a handheld app package. Im just trying to reference a Library I created from an android App I created. I cant find any settings in either the csproj file the sln or the IDE that have changed that made my driod library into a wearable library (Im sure I changed something just dont know what) Its here somewhere just no idea were or what I'm looking for besides scanning for the word wear which doesn't seem to show up anywhere. I looked back through my change history and I dont see where it got messed up at.
Until last week everything was fine. Then I started trying to get the latest release of Xamarin.Forms to allow my code to compile. I changed a number of settings over a week of debugging that issue and finally got everything to work again by setting my target Platform to 6.0 and downloading the latest Android SDK.
The Libraries I'm attempting to reference that cause the issue I have on GitHub # https://github.com/Indiponics/IndiXam-Lib in case anyone cares to look at the csproj file etc.
The solution is easy. Open the .csproj file of your Android app and find the project reference you need to work. It might look like this:
<ProjectReference Include="..\MyWearApp\MyWearApp.csproj">
<Project>{D80E1FEF-653B-448C-B2AA-609C74E88340}</Project>
<Name>MyWearApp</Name>
<IsAppExtension>True</IsAppExtension>
</ProjectReference>
The problem is with the extension part. Simply remove the IsAppExtension line and any other than Project and Name. It should work now.
I think we lost an entire man-week on this issue!
https://developer.xamarin.com/guides/android/wear/working-with/packaging/
Short Version: I'm having issues while archiving my application. The debug works, the archive doesn't. There is nothing to troubleshoot, anyone has ideas?
Log Version:
I have a hybrid worklight app, fully functional and archiving was working just fine until I've added MQA and I'm using iOS.
Versions are:
Worklight 6.2, MQA 6.3, Xcode 6.1, and iOS 8.1.2
Now I've added MQA following the steps here.
I've copied the framework into my project directory and added in the other_linked_flags a force load for it.
I've also added a few lines of code to for it to work following the same instructions. Basically everything works just fine when I run it from xcode. When I run the app that xcode deploys on iphone, it the app runs normally and MQA also works.
I only have some kind of problem when I try to archive the app to deploy it in a ad hoc environment.
When I do that the iPhone screen remains black after asking me which user it should use on the MQA. It seems that it can load the webview but can't load the html app.
Unfortunately this doesn't even generate a crash log an as such I'm left in the dark about what is happening.
Can someone give me some light on what can I do to troubleshoot this issue?
You may be trying to integration the wrong library into your project.
Right now it looks like you are working on a Hybrid app but try adding the native libraries into it, which is incorrect.
If you are working on a Hybrid app, you need to download the Hybrid SDK.
If you are working on a Native iOS app, you need to add the native library
There is a library specific to Hybrid apps. You can find it in the following link: http://www-01.ibm.com/support/knowledgecenter/SSFRDS_6.3.0/com.ibm.mqa.uau.doc/topics/t_download_wrklight_libraries.html?lang=en
All what is required is to do is removing the native library if added, and integrate the worklight SDK into the app code under the common folder in the main.js file.