How to testflight ios on m1? I still get issue nonzero - flutter

I get the major problem cause i can't deploy testflight ios, error said nonzero, i've tried to resolve but still error i don't it is minor or major because i new user on m1, let see pict on below :

This can happen because of many reasons. One common solution is to delete Podfile.lock file, Pods directory and .symlinks folder and run pod install again and build it.

Related

Suddenly can no longer compile - No such module 'SDWebImage'

So suddenly my project stopped working and I have no idea why and I'm running out of ideas.
I've found some blogs 1 2 and similar requests 1 2 3 for help but nothing seems to work for me. I may be doing something wrong though.
running xcode 13.4.1
I've got 4 distinct errors
Command EmitSwiftModule failed with a nonzero exit code
error: accessing build database "/Users/myuser/Library/Developer/Xcode/DerivedData/App-btdfdbatbdurmeawknwdwmjrqpsw/Build/Intermediates.noindex/XCBuildData/build.db": disk I/O error
Virtual filesystem overlay file '/Users/myuser/Library/Developer/Xcode/DerivedData/App-btdfdbatbdurmeawknwdwmjrqpsw/Build/Intermediates.noindex/App.build/Debug-iphoneos/App DEV.build/all-product-headers.yaml' not found
/Users/myuser/myapp-ios-app/App/UI/Feed/FeedVC/FeedVC.swift:11:8: No such module 'SDWebImage'
I believe the EmitSwiftModule is related with not being able to handle the pod therefore causing the issue in the "all-product-headers.yaml" which is generated to fetch all the pods headers?
So assuming that all things in derived date are as they should be (because i've deleted it) I tried to focus on why is the pod no longer compiling. To my co-worker is working fine. Maybe he will have the same issue if he deletes the derivedData? Maybe we are using some older version files?
Some things I've tried:
clean the project
reset pods cache
delete derived data folder
update the pods
clean xcode preferences
for this pod they say we should add :modular_headers => true in pod file
re download the project clean to another folder
instead of cocoapods use the package manager for SDWebImage
due "all-product-headers.yaml" issue i read here that i could just add a header to my project
I've tried to create a project from scratch and just use the same pods and the project seems to run fine. But this is not a solution.
Can someone please help me? Any ideas?

CompiledSwiftSources failed with a non-zero exit code

I was recently using Xcode 13.4.1. Downloaded and installed the 14.3 beta. Deleted the beta completely, ran 13.4.1 and it wouldn’t build my project anymore. I don't receive any “errors”, I just get a warning saying, “Could not read serialized diagnostics file: error(“Failed to open diagnostics file”).” for a couple of my package dependencies(no specific package, shows the error for different ones everytime I try to build). Or sometimes I get the warning above AND an error that says, “CompiledSwiftSources failed with a non-zero exit code”.
At one point, I did see this warning, “Failed to retrieve search paths with pkg-config; maybe pkg-config is not installed.” I'm not seeing it anymore, but maybe it still applies?
I've tried cleaning my project, reset packages cache, deleting derived data, restarting Xcode, restarting my machine, deleting 13.4.1 and re-downloading it. No cigar.
Anyone else run into this and/or have an idea on how to resolve this?

No such module Crashlytics - Pod seems to be missing

I constantly get an error "No such module Crashlytics" and I usually resolve it with hours of cleaning build folder, reinstalling everything, running pod install, etc, but I'm getting tired of this and want to fix the problem once and for all.
My podfile contains this entry:
pod 'Crashlytics', '~> 3.14.0'
I suspect the issue may be that my project is in an icloud directory and sometimes it doesn't download everything locally in an attempt to save drive space, but either way here is what I am seeing and would like some help:
My pods in navigation tree (notice Crashlytics)
Now what's interesting is that when I go to add the framework directly (Link Binary with Libraries) that all the other modules are there in my Pods location except Crashlytics!
So here you see it's not there in Pods!
Any ideas what's going on? I suspect this is an important reason why it is not seeing this.
Thank you!
Try to do the following:
Delete all 4 pods related files:
Podfile
Podfile.lock
yourprojectname.xcworkspace
Pods folder
Then reinstall everything again with pod init and pod install

How to handle a PBXCp error with EarlGrey?

I keep getting this error recently when I did a pod update, pod install and then executed my test cases using EarlGrey.
And when I try to resolve the path with terminal, I do not have anything in that path, nor do I have a EarlGrey-1.0.0 in my system.
The answer for the same seems to be a simple one.
Although had to struggle a lot to find and a lot of going back and forth with EarlGrey dev team.
First step is to fix the 'podfile'.
Details below:
My podfile used to look like this while I encountered the problem.
And couldn't possibly figure out. Deleted 'Podfile.lock' and 'Pods' folder repeatedly and performed 'Pod update' and 'Pod install'. No luck.
Then I tried changing the path in "EarlGrey Copy Files" in Build Phases by browsing the 'framework' directly from my finder. Although that could solve my problem temporarily, it wasn't permanent. I checked my schemes to make sure if nothing got messed up there!
If all these are intact, then the problem is with podfile. As per the instructions mentioned here: https://github.com/google/EarlGrey/blob/master/docs/install-and-run.md#step-2-add-earlgrey-as-a-framework-dependency
or have a look at my fixed podfile below:
Add this line as mentioned in the post install hook. Then do a pod install and clean build, should fix the problem.
although the above change may fix the problem, but after earlgrey gem 0.2 release, the integration process should be a lot smoother w/o any post_install or require in your Podfile.
for more info here

Installing IPA results in error "A signed resource has been added, modified, or deleted"

I've recently stumbled upon a rather odd problem with Xcode which occurs when I build an IPA and attempt to install it, I've tried installing using Xcode, iTunes and iPhone Config Utility, all of which give the same error
A signed resource has been added, modified, or deleted.
I can successfully debug the app on my phone using XCode, it's only when I try to install an IPA I see the error.
I've tried unzipping the IPA and running the codesign validation tool which throws up the following response:
a sealed resource is missing or invalid In architecture: armv7
resource missing:
/Users/dev1/Documents/PoleTester.app/Settings.bundle/._Root.plist
This led me to look at the Settings.bundle file and ensure that it's being included in the build, which it is. Interestingly though, if I remove the Settings.bundle file, build an IPA and attempt to install it on my iPhone the install succeeds, however this of no use as I need the Settings.bundle file installing with the app.
Further investigations on some of my previous XCode projects has shown that I can build an IPA, with the Settings.bundle file included, and successfully install it. However, if I make a simple change to the Settings.bundle file, such as adding or removing a row, build an IPA and then attempt to install it I get the
"A signed resource has been added, modified, or deleted" error.
I'm at a bit of a loss as to what's causing this error and why the Settings.bundle file is causing the install to fail.
Has anyone seen this error before or potentially shed some light on what's causing it?
I'm using Xcode 4.6.3 and an iPhone 4 running iOS 6.1.3.
Clean Build Folder (⌘⌥⇧-K) has resolved this for me 3 out of 3 times.
I just ran into this issue using Xcode 6 beta 6 installing to my iPhone 5 running iOS 8 beta 5. The app I'm building uses a Today extension (aka widget).
It appears the issue stemmed from my having not set up dependencies properly. I have a third party framework (Alamofire) set up as part of the project as a dependency of the overall project, but not as a dependency of the today widget. I could build fine but when installing to device I would get this "signed resource has been..." error.
By adding Alamofire as a dependency of the Today widget this resolved the issue.
It's a bit late but I ran into the exact same issue today with Xcode 5.0.1.
According to https://developer.apple.com/library/ios/technotes/tn2318/index.html, "the resource missing: my.app/..*" error could be caused by:
The file prefixed with "._" is considered an AppleDouble file and it can result from copying the uncompressed Xcode project folder onto a non-HFS+ formatted disk. The AppleDouble files must be removed using the 'dot_clean' command. The Xcode project folder is the argument to dot_clean as illustrated below.
Steps I did to resolve this:
Close Xcode
Run "dot_clean /path/to/My_Xcode_Project" in Terminal
Open Xcode again and make a new build
Oddly enough most of these _* files don't seem to cause any issues except those inside Settings.bundle (Nearly every file in my directory had one, but only after I added Settings.bundle, the IPA failed to install).
I also faced the same issue and this post solved my problem:
http://code-ninja.org/blog/2012/04/17/signed-resource-has-been-added-modified-or-deleted/
It turns out that the problem was caused by having special character in the product name – in my case, a ?. Removing the ? from the product name fixed the problem.
In my case, what helped was adding a bash script into build phases (just before "compile sources"):
find ~/Library/Developer/Xcode/DerivedData -name "YouAppName.appex" | xargs -I % find % -type f -maxdepth 1 | xargs rm
What this script does, is to clean files in project's appex dir (e.g. assets), but leaving sub-directories (e.g. compiled storyboard). In effect, using this script while building is much faster to execute than full project clean.