I've got this error:
Fabric: This app relies on Fabric. Please sign up for access at https://fabric.io/sign_up,
install Fabric.app then ask a team member to invite you to this app's organization.
If this machine is a build server please remove Fabric.app if present and use xcodebuild so that Portfolium.app.dSYM is uploaded.
Command /bin/sh failed with exit code 1
But I have logged in in fabric app and it works for me before.
I supposed I delete app to trash. That's why it caused this issue.
Again install fabric app in simulator.
please follow this
please find fabric in spotlight and and run again and try it.
also go check with this link
How to integrate fabric with Xcode 6.2
Related
I'm using EAS to build my Expo app, and today I started getting this error when attempting to run an iOS build, either local or on EAS servers. I'm thinking it's an issue with Apple servers, so I'm hoping it gets fixed soon.
Output from build command:
✔ Select platform › iOS
✔ Using remote iOS credentials (Expo server)
If you provide your Apple account credentials we will be able to generate all necessary build credentials and fully validate them.
This is optional, but without Apple account access you will need to provide all the missing values manually and we can only run minimal validation on them.
✔ Do you want to log in to your Apple account? … yes
› Log in to your Apple Developer account to continue
✔ Apple ID: … ...
› Restoring session /Users/.../.app-store/auth/.../cookie
› Session expired Local session
› Using password for ... from your local Keychain
Learn more
✔ Logged in New session
Authentication with Apple Developer Portal failed!
Error: Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com
Anyone else have this problem and have any ideas on how to resolve it?
I've tried removing the stored authentication cookie and signing in again. I also tried signing in on App Store Connect to see if there was any issue with my account but I couldn't find one.
Updating the eas-cli version to version 3.5.2 fixed the problem for me.
Just run the command:
npm install -g eas-cli
and it supposed to work
I was getting the same error. I was able to start the build, after selecting no for the "Do you want to log in to your Apple account?" question. I hope this workaround works for you.
github issue https://github.com/expo/eas-cli/issues/1672#issuecomment-1416851869
Edit: As #Dviros pointed out above, run npm install -g eas-cli for a definitive solution.
I started having this issue today too.
There is old issue in github that seems to be related
https://github.com/expo/eas-cli/issues/1220#issuecomment-1416834395
Looks like it just started happening again today.
This is now fixed by the expo team.
In order for it to work, all you have to do is update to the latest eas-cli. This should do it:
npm i -g eas-cli
Then build or submit you application to iOS.
eas build --platform ios --auto-submit
Of course you can ignore the --auto-submit.
I was able to work around the Apple sign in by using local credentials.
https://docs.expo.dev/app-signing/local-credentials/
By going to the Expo website I was able to download the distribution certificate and provisioning profile certificate. There was also a file that had the password needed to access the distribution certificate. Then I configured the production build profile in eas.json with
...
"ios": {
"credentialsSource": "local"
},
...
And I created a credentials.json file with
{
"ios": {
"provisioningProfilePath": "relative/path/to/provisioning/profile.mobileprovision",
"distributionCertificate": {
"path": "relative/path/to/distribution/certificate.p12",
"password": "<MYPASSWORD>"
}
}
}
Then building with the normal command, it no longer prompted me to sign in to Apple. Build worked like a charm!
I wont advise to put the password in a file, it's a dangerous practice.
I guess the Expo EAS team will need to have a look and find a solution for all of us users.
The EXPO team created an incident on there status page regarding this issue:
Apple authentication error renewing certificates/profiles for EAS Build
We are currently investigating an upstream issue authenticating with Apple to renew certificates/profiles when using EAS Build.
If you are using local credentials, if you're running a non-interactive build, or if you don't need to login to Apple because your certificates/profiles are up to date, then you are unaffected by this incident.
I hope they fix it soon!
use Transporter.
I got the same issue, but i solved it using transporter. I use eas build to upload it to expo server from there i download the app and upload it to Transporter.
Reinstalling eas-cli globally using npm i -g eas-cli did not fix this problem for me.
I was able to fix this by updating the eas-cli package in my local project.
Update your package.json to "eas-cli": "^3.5.2", and then run npm i to reinstall.
I tried to build my expo project on XCode so I ejected that and open in XCode using xed ios. but when I tried to build it and run it show's me that build was successful but on simulator it stuck at '100%' and wont run. also on XCode I receive this:
"expo-updates must be configured with a valid update URL or scope key."
how can I solve this issue?
It is an expo issue, the solution found is:
Sign in to your expo account in expo-cli and it will configure expo-updates properly when you eject. You can fix this on an already ejected project after signing in by running expo eject --no-install.
Or
Check JWrubel comments for the same issue below.
I was able to get around this issue without doing expo login by editing ios/<AppName>/Supporting/Expo.plist and adding a key for EXUpdatesURL like so:
<key>EXUpdatesURL</key>
<string>https://example.com</string>
This causes the update check to fail, but the build to succeed. I tried setting EXUpdatesEnabled to false and EXUpdatesCheckOnLaunch to NEVER, but I didn't find those had any impact on the process.
/Users/Alex/Library/Developer/Xcode/DerivedData/MyProject-ehabmnclpzlywhabrefntacibonm/Build/Intermediates.noindex/ArchiveIntermediates/Fuego/InstallationBuildProductsLocation/Applications//MyProject.app/Frameworks/Alamofire.framework: unknown error -1=ffffffffffffffff
Command /bin/sh failed with exit code 1
I got this issue when I Archive my project. When I run app on simulator it works ok without such issue above.
Also it works ok with Xcode 8, but now when I try to Archive it on Xcode 9 I have this issue. But maybe this is not the case as I reinstall Mac OS from scratch, so it maybe cocopods version issue I am not sure.
Also two // here in the example above is also strange for me /Applications//MyProject.app
I believe it's a Xcode's bug. Restart your Mac and try to build again. Xcode would ask permission to access your Keychain before build Alamofire, then just allow it.
Hm it's very strange after some search on the Web I found that this is actually signing issue.
I used Xcode to generate new distribution certificate and maybe this leads some problems for me.
What I did to solve my issue.
I removed all certificates on my Mac and in my apple account.
I removed all prov profiles as well on my Mac and in my apple account.
I requested certificate and save it on the disc manually (not via Xcode )
I recreated certificate and profile. Downloaded it manually and double click on it.
After that I faced with keychain issue when I can not enter password to allow signing my certificate. I use this link to move certificate form login to system section.
Finally I get it work.
I am having an issue running my app on the device after installing the "cordova-plugin-mfp-push".
In Xcode , I see the error..
Unable to install "my app"
the certificate used to sign "myapp" has either expired or has been revoked. An updated certificate is required to sign and install the application.
When I remove the plugin the error goes away and I can deploy to my phone.
Can you give some hints on how to debug this issue. My certs is valid and push is enable for the certs.
I am using MobileFirst version 8 , xCode 7.3 with the mfp template
Thanks for your help
To help propagate the changes that are added by the push framework removing the ios environment and adding it back in has resolved a similar issue in my environment:
$ cordova remove ios
$ cordova add ios#latest
Once you have re added the ios platform run cordova prepare and cordova build ios
Once the above steps are completed you can open the project in Xcode. Here Xcode will find two warnings that can be automatically handled by Xcode that are worth updating. Review what will be updated and correct the warnings. See image below:
At this point you should be able to run the project successfully.
dUsing APNS requires the Push Notification capability and therefore a new certificate. You can renew the certificate within the Apple Developer Portal (Certificates, Identifiers & Profiles).
Alternatively you could use Xcode 8 which simplifies certificate handling a lot when using automatic code signing.
I was facing the same issue. After adding mfp-push plugin I was unable to install the app on iPhone with error saying "The application does not have valid signature".
I could resolve this by removing cordoba-plugin-mfp-push & also cordova-plugin-mfp, then adding only cordova-plugin-mfp-push, which in turn adds cordova-plugin-mfp.
I'm practicing with this new programming framework called NativeScript, which allows creating native apps using JS. However, when I started working on the Hello World tutorial, I got this error:
https://gist.github.com/longpham91/d603c8fe7f6c6b06e86f
The error occurred when I tried running command "tns run ios" on Terminal, which basically allowed NativeScript to run HelloWorld app on my phone.
I also looked at the error log, and it seemed that the error might have something to do with my Xcode device settings, as explained here:
Check dependencies Code Sign error: No code signing identities found:
No valid signing identities (i.e. certificate and private key pair)
matching the team ID “(null)” were found. CodeSign error: code signing
is required for product type 'Application' in SDK 'iOS 8.4'
I'm not sure what this means, though.
I was able to figure this out after posting a thread on {N} Google group. Here's how:
Generate the Certificate and Provisioning Profile, following this tutorial: http://seventhsoulmountain.blogspot.no/2013/09/ios-code-sign-in-complete-walkthrough.html
Go into the iOS section of your {N} project (under platforms/ios), and run the .xcodeproject file. You can also make a copy of this folder, to be sure that you don't accidentally change something in the source code.
When the Xcode project is opened, go to Xcode > Preferences > Accounts, and click on View Details.
Add the Provisioning Profile by clicking the + button.
That's all. Took me a while to figure this out since I'm not all that familiar with Xcode, but your project should run on your iOS device now.
Not sure, but I think the PATH variable "android / tools and android / platform-tools /" do not exist. You can use the android command in your shell?