xcode build not compiling due to pods unity-iphone-framework.sh line 42 source: unbound variable - ios

Basically, I made a game on unity and then when I built it for Xcode it showed up this error after I updated the pods file and excluded the arm64 architecture, can someone please guide me on how to fix this error
I have already tried on m1 mac and an intel based mac but the same problem occurs I have reinstalled pods and also have rebuilt the project but nothing seems to work

Upgrade all Pods to the latest version available.
Delete the "VALID_ARCHS" from build settings and user define settings

Related

Building Realm for Mac Catalyst fails: Realm.h not found

I have an iOS app, which I recently updated to support Mac Catalyst. For the Mac version I added a new target, which I also added to my Podfile with the subset of the same libraries, including Realm.
The app builds well for "My Mac", but when I want to archive it (build for release), it fails with the following error:
"Umbrella header 'Realm.h' not found"
I am not familiar with the problem, what could go wrong?
I tried the usual Derived Data deleting, etc, but nothing seems to help. Is this some kind of problem with the CocoaPods, my config, or with Realm?
Due to CocoaPods not releasing 1.10.2 I have fixed the same issue in my project.
Remove Realm from your pod file
pod install in terminal to remove it fully
Install Swift Package Manager for (Xcode) - https://swiftpackageregistry.com/realm/realm-cocoa
This should allow you to get the project archived successfully.

importing "Module 'app_settings'" not found

I'm currently trying to work with xcode to test my flutter application with xcode. The big issue is that all of my imports (such as app_settings, cloud_firestore, etc...) give an error for "Module ___ not found". When I try to run my dart code I get the error in the terminal:
[Proj Root]/ios/Runner/GeneratedPluginRegistrant.m:10:9: fatal error: module 'app_settings' not found
#import app_settings;
~~~~~~~~^~~~~~~~~~~~
1 error generated.
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
I tried running flutter create for ios, (this might've made things worse?) Flutter clean and reinstalling pods doesn't seem to work either. I'm wondering if there's something simple that I missed with importing modules. I created the application on android using modules that should work with Android & iOS. After getting the android version working I pulled my project on my mac through github and finally reached this issue. Any pointers would be appreciated because I'm totally stuck on this.
My project has 3 build flavor. Development, Staging & Production.
In Xcode It was selected default Runner One. (On Top of the middle)
though i follow the process like
delete pod , Podfile.lock and .symlinks from Android Studio / (From Project)
flutter pub get
cd ios > pod install
Then In XCode > clean build
Select Right Build Flavor (Production For Me)
Then Archive (Done)
NB: I tested in M1 machine.
Hmm Not sure what happened but it seems to be good now. I think pod init was initializing minimal data for the podfile. Instead, I deleted the Pods file and did flutter run and it built the podfile correctly with flutter pub get.
Had the same problem, we solved it by setting the iOS Deployment target in XCode to the same value as set in the Podfile, which was 12.0. Then ran flutter clean and flutter build ios worked like a charm 🎉
I had this same problem. What I did was
Delete the Podfile and Podfile.lock
flutter clean
flutter build ios
Opened the Runner.xcworkspace
Build on Xcode
This worked for me 🎉
Delete pod directory and podfile.lock
flutter clean
flutter pub get
cd ios
pod install --repo-update
run the application in Xcode
I tried everything above, but for me the solution was quite different.
I am using flavors (schemes), and I accidentally created the scheme with upper case in the first character, while everywhere else (build config etc.) I used lower cases only. After deleting the scheme and recreating with lower case characters, it worked.
path/flutter/ios/Runner/GeneratedPluginRegistrant.m:12:9: Module 'app_settings' not found
I had the same issue after upgrading the Xcode to 13.3 and my production build flavor wasn't working. I was using firebase as well. In my production build flavor, I didn't append anything to the configuration name (i.e. all the other configurations have the name like "Debug-staging", "Debug-development", but in the production, it's only "Debug"). I just deleted the pod file and run:
flutter run --flavor production --target lib/main_production.dart
Everything worked fine for me.

How to manually download GitHub iOS code and have it work in XCode 11.7?

INTRO
Greetings!
I have recently been granted access to a proprietary (that is, private) GitHub repository for iOS development. I'm on a Mac (OS 10.15.6 Catalina, the latest MacOS as of this writing) with the latest non-beta XCode version installed today (11.7) as well as the latest iOS emulator as of this writing (iOS 13.7). I am new at using Macs, at XCode, and working with this project, and the author of this GitHub code hasn't been available to help me work with his code. (I am well familiar with downloading files from GitHub and the Internet in general.)
I know this GitHub repo has XCode inside because there's an XCode file, Pods.xcodeproj. There are also many other files, including .xcconfig files.
It may be a hardware problem. This Mac's technical specs were minimalistic: It has less than 4 gig of physical RAM and a recently-obtained hard disk space upgrade to put it around 70 gig of total space, or enough to work with Android Studio and XCode. (A sample project failed to run in the simulator due to having too little RAM.)
Thus, what's wrong and how should it be fixed?
Thankee!
ERROR MESSAGE
Build target hornet of project hornet with configuration Release
error: /Users/Liam/Desktop/HORNET/9-1-20/ios/Pods/Target Support Files/Pods-hornet/Pods-hornet.release.xcconfig: unable to open file (in target "hornet" in project "hornet") (in target 'hornet' from project 'hornet')
error: /Users/Liam/Desktop/HORNET/9-1-20/ios/Pods/Target Support Files/Pods-hornet/Pods-hornet.release.xcconfig: unable to open file (in target "hornet" in project "hornet") (in target 'hornet' from project 'hornet')
error: /Users/Liam/Desktop/HORNET/9-1-20/ios/Pods/Target Support Files/Pods-hornet/Pods-hornet.release.xcconfig: unable to open file (in target "hornet" in project "hornet") (in target 'hornet' from project 'hornet')
error: /Users/Liam/Desktop/HORNET/9-1-20/ios/Pods/Target Support Files/Pods-hornet/Pods-hornet.release.xcconfig: unable to open file (in target "hornet" in project "hornet") (in target 'hornet' from project 'hornet')
The presence of the Pods path suggests the project is using CocoaPods. If so,
If you haven’t already, install CocoaPods.
Once that’s installed on your computer, go to the project root folder in Terminal and run pod install to download the pods.
In Xcode, open the .xcworkspace, not the .xcodeproj.
But 4gb of RAM may simply be too modest to use Xcode at all. If you can’t create and run a simple test project in Xcode, you certainly won’t be able to open a bigger project. My recollection was a 8gb minimum, but even that will struggle. 16gb is pretty decent and if you can afford more, so much the better.

Problems building through bitrise; more problems building through xcode

I've somehow found myself trying to build an app through bitrise to deploy to testflight. I'm a total novice at all of this, so apologies for what probably seems stupid.
Bitrise manages to build everything but then finally refuses to deploy, citing the following in the log:
[06:06:44]: [Transporter Error Output]: description length:10500450
[06:08:55]: [Transporter Error Output]: ERROR ITMS-90725: "SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later."
[06:08:55]: Transporter transfer failed.
[06:08:55]:
[06:08:55]: description length:10500450
ERROR ITMS-90725: "SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later."
Fine, I think, I'll clone the repo, open up the project in xcode and thereby update the sdk version. This just seems to mean more problems... When I try to build the project within Xcode, I encounter the following error:
Users/[...]/ios/Pods/Target Support Files/Pods-x/Pods-x.debug.xxconfig: unable to open file (in target "x" in project "x")(in target 'x')
In addition to this, there are a few issues, including:
The file "Pods-x.release.xcconfig" couldn't be opened because there is no such file.
If I ignore this error, push it and build it anew on bitrise, I get the following:
Resolving dependencies of `Podfile`
[!] CocoaPods could not find compatible versions for pod "DoubleConversion":
In snapshot (Podfile.lock):
DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)
In Podfile:
DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)
None of your spec sources contain a spec satisfying the dependencies: `DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`), DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)`.
You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* mistyped the name or version.
* not added the source repo that hosts the Podspec to your Podfile.
Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.
So, it's looking like there's something badly amiss with the CocoaPods installation. And indeed, when I check into the files, there is no Pods folder at all -- just Podfile and Podfile.lock. (I have no idea how it would have build fine previously without this?)
So, I try to reinstall CocoaPods into the project, by running pod install from a terminal in the iOS folder. I get that same error in the terminal: No such file or directory # rb_sysopen -- /Users/[...]DoubleConversion.podspec. pod update generates the same error. In addition, I'm told there's a new version of CocoaPods available. I install it using sudo gem install cocoapods, which generates a Pods folder with subfolders in ios, but all are empty.
As you can tell, I'm a bit baffled. If an intrinsic part of CocoaPods functionality is missing from the project files, how did it ever build previously? I'm guessing it's due to CocoaPods being installed as part of the bitrise workflow (and it is indeed there) -- but, if so, what about that is now causing it to fail during build? What is it about trying to open up the project to update the SDK used that is introducing this problem?
I'm sure all this seems a bit daft (at least I hope so). Thanks for your patience and any help would be enormously appreciated.

Xcode Dependencies Error

I was having an issue changing my Target Deployment to 8.4 (its been 9.1since I started the project). I was getting an error saying Parse was setup to use 9.1 so I couldn't change it. Then I changed the platform information in my podfile and reinstalled the pods. Now I am getting these two errors when I try and Build the app.
Check dependencies
Unable to run command 'CpResource RLA\ Volunteer.app' - this target might include its own product.
Unable to run command 'Touch RLA\ Volunteer.app' - this target might include its
own product.
Any help is welcome.
I'm running Xcode 7.1.1 on a Macbook Pro and coding in Swift.
I figured it out. My .app file in my Product folder in Xcode had a selected target. I don't really understand why it worked by unselecting a Target Membership (so nothing is selected when I select the .app file) fixed the dependency errors.

Resources