Framework gets deleted from app bundle after redeploy on Xamarin.iOS - xamarin

After cleaning the build and deploying the app for the first time (both on a physical device and a simulator), it works the way it's supposed to. But after I change something and redeploy, SkiaSharp (libSkiaSharp.framework) and Realm (realm-wrappers.framework) don't get added to the app bundle Frameworks folder.
Other frameworks get added as usual after redeploys, but these two don't.
I already tried to disable incremental builds and device-specific builds, and it didn't fix it. I don't have a clue why this is happening.

After updating to Xamarin.Forms 4.8 the issue was fixed.

Related

Is the AgoraRTMWrapper in XCode necessary?

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?

How to remove a "zombie" framework from an Xcode/Swift build

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?

React Native assembleRelease app::bundleReleaseJsAndAssets never progress

I'm trying to generate release version of my app using React-native :
./gradlew assembleRelease
It's progress until app::bundleReleaseJsAndAssets gets stuck at 93% and never progress. I dont have any error on terminal.
About OS I'm on Mac OS.
issue reported https://github.com/facebook/react-native/issues/10078
If you are using realm, please consider that comment:
:app:bundleReleaseJsAndAssets was trying to bundle the default.realm* in the root folder generated from the tests in jest... So it was hanging there.
It couldn't decompile them or whatever. So i just deleted them and it worked again
I used to have realm in my project but removed it. I still had files not tracked by git, hanging around. I simply removed everything related to realm and it worked again
If you are building the react native app in android studio and you are stuck at
app::bundleReleaseJsAndAssets never progress
It could be the issue with "CMD" in the android studio. Please Make sure you install the plugin.
I'm able to resolve the issue.

MQA fails after archiving application in XCode

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.

Packaging error when switching to arm64 (arm5 was OK)

I just plugged in a new iPhone 6, created a provisioning profile and then I launched the app I'm developing on the device. It compiled fine, but at linking stage it errored out with:
ProcessProductPackaging
...
error: class '(null)' of input object does not respond to either selector writeToFile:options:error: or writeToFile:atomically
I cannot find any information of what that is. I do not get any specific code reference to relate it to. Did anyone experience this?
Personally I was able to solve this issue by rebuilding the project a second time. I think I was only experiencing it after revoking and requesting a certificate.
Odd for it to jump at me and disappear though.
I just restarted Xcode then the error was disappeared
I've tried turning the "Automatically managed signing" off and on again, then the issue disappeared. Note: rebuilding didn't help for me, cleaning either.
I removed an external library and related code I had and it's now working.
I just changed some provisioning setting and then restarted the xcode afterwards the error was disappeared and archived and then uploaded successfully
Rebuilding the project does the job for me. Actually I was making changes in capabilities while Xcode was building that makes build failed.
The error occurred after I made manual changes to the Xcode .entitlements and Info.plist files: I removed some entries. None of the above mentioned solution attempts worked for me. Every try to create an archive failed.
The solution was to go to Xcode's Capabilities section and switched everything on and off again.
I had the same problem specifically on an App Extension we used for Push Notifications, and I was using Automatically manage signing but it seems the App Groups in capabilities were failing, so I just had to make sure the App Groups were retrieved correctly and this fix it.
Also if you have .entitlements files, and you have App Groups there, make sure they are the same you are using in the capabilities configuration.
Restarted XCode and enabled and disabled to Automatically manage signing

Resources