I signed an iOS App and WatchKit App & Extension targets with valid provisioning profiles (Separate provisioning profile for each app identifier, and not wild card App ID), Build was archived successfully but when I try to export/save Enterprise build, Xcode auto generate/locate XC: provisioning profile and it also and resets/invalidates previously selected provisioning profiles. I get below error. (even though we are not using Wild Card App IDs)
"Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles".
It seems like it is bug in Xcode 7.2 , after trying multiple times and troubleshooting , below solution worked for me.
1) Open Xcode preference
2) Select the team
3) Click the "View Details.."
4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.
5) In section "Provisioning Profiles". Click on "Download All".
6) Restart the Xcode.
7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.
For more detail find Screenshots below:
1) Open Xcode preference,
2) Select the team,
3) Click the "View Details..".
4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.
Delete Provisioning Profiles
5) In section "Provisioning Profiles". Click on "Download All".
6) Restart the Xcode. (most of the times Restarting Xcode is only solution after downloading new provisioning profiles or after changing App identifiers)
7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.
Hope it solves your problem. :)
P.S: I've also opened a bug to Apple via Apple Bug Reporter.
Related
I have a download link for an app (ad hoc, only to work on a few designated devices for testing). I have configured my plist file correctly, so the app itself downloads and installs without any issues. However, I think due to it being ad hoc, it does not install the certificate needed to run the app (I currently get the untrusted developer alert, and their is no certificate in general settings for me to trust).
So I tried to add a link for the provisioning profile on the same download page. Clicking on the link in the browser brings up an alert saying that Settings wants to show me a configuration profile. I click allow and it takes me to the Profile area in General settings, but there is nothing there.
How would I go about creating a simple link to download the profile onto the device? The code I used for the link is pretty straight forward.
Profile
Can anybody help? Many thanks in advance.
So I tried to add a link for the provisioning profile on the same download page.
You are not in a right direction. No one will ever do such download profile thing.
For Ad Hoc build, you have to add your desired devices to your ad hoc provisioning profile. I assume you did not do it so you can download the app but cannot install it.
So check your developer certificate portal and remember to re-generate your provisioning profile having these devices checked. And then build the app again with the new provisioning profile.
So it turns out that the issue was when I was archiving the project from Xcode to an IPA file. I was using the default setting for the developer certificate that I should be signing my app with. It also had a dropdown list to select a second certificate (which as far as I can tell is still the same certificate). Selecting the second one seemed to sort the issue out, where as the default option for some reason did not include the certificate with my IPA file. Not sure why it worked this way, to be honest. App now installs and runs without any issues.
Can you help me get my crashes symbolicated?
In Xcode 7.3, Window -> Organizer -> Crashes, I have crash reports from my latest TestFlight builds. They were built on this Mac, and all the archives with the corresponding dSYMs are in the Archives tab. The app is divided into a number of frameworks and the main app, and many are a mix of Swift and Objective C. In the crash log I can see the name of the frameworks and app listed correctly, but all the entries for my frameworks and app are in hex. UIKit is symbolicated just fine.
When I look in iTunes Connect, it says "Yes" to "Includes Symbols" and allows me to download the dSYMs. When building, the "Debug Information Format" option was set to "DWARF with dSYM". I tried setting "Strip Debug Symbols During Copy"
and "Strip Linked Product" to "No" to see if that made a difference. It didn't.
I cannot find the symbolicatecrash app on my system, not even in /usr/bin or /Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash, but I have an older Xcode 5 where I could grab it. However, it does not resolve the symbols anymore.
I have the same problem in Instruments, if I profile my app, UIKit is symbolicated just fine, but my frameworks and app only show hex.
I know there have been a lot of posts about this, but I have going through them a lot from the 7.3 beta period and until now and have not found a solution
The location of symbolicatecrash has changed in Xcode 7.3:
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
After reading this:
https://developer.apple.com/library/content/technotes/tn2151/_index.html
you find out that the App Store is responsible for symbolicating crash reports that come from TestFlight – not Xcode. And it appears the App Store is very unreliable at doing it.
Here's a workaround.
Go to the Archives tab in the "Organizer" window and make sure that for whatever build you need to symbolicate a crash report for, you have clicked the "Download dSYMS..." button over on the right side of the page. This is required if you are uploading in BitCode.
Attach an iOS device so that it appears in the "Devices" window.
Select the device and click "View Device Logs".
Now, go back to the Organizer Window, select the "Crashes" tab and select one of the crashes that did not get symbolicated.
Right-click on it and select "Show in Finder".
Right-click on the revealed .xccrashpoint bundle and select "Show Package Contents".
Drill down into DistributionInfos -> all -> Logs.
Drag any of the .crash files into the left side of the "View Device Logs" pane open in the Devices window.
Wait a second or two for Xcode to symbolicate the crash.
Same here. Having a hard time finding the symbolicatecrash after upgrading to 7.3.
However, you can still use the atos though.
You can find the tutorial here Symbolicate crash in iOS8 with Xcode 6 .1
I do not upload symbols with my application, so the App Store cannot symbolicate for me. I used the following workaround to symbolicate all of the crashlogs that XCode downloads from the store. These instructions are for XCode 8. The paths for the symbolicate crash app will vary from version to version of XCode but the ideas should be the same in each version.
Place your symbols where the symbolicator can find them: Place your symbols (.dsym) file in your Archives directory. You can find this by going to Organizer, context clicking on an archive and choosing "show in finder". Navigate up to the Archives directory (e.g. /Users/USERNAME/Library/Developer/Xcode/Archives) and place your dsym file there. It can be in other locations as well, it's just that I've verified that this one works.
Download the crash logs: In XCode, make sure that you've downloaded the crashlogs for the build you want to symbolicate (Organizer->Crashes, click on your app and then choose the version of your app in the panel to the right of the list of apps).
Locate the crash logs on disk: In the panel that has the App Version and build number, context click on one of the crashes and choose "Show in Finder". Navigate up to the "Crashes Folder" and note this location e.g.: /Users/USERNAME/Library/Developer/Xcode/Products/com.company-name.Your-App/VERSION/Crashes
Setup DEVELOPER_DIR for symbolicatecrash on the command line: Open a terminal window and CD to the crashes directory from step 3 and set the DEVELOPER_DIR like this: cd /Users/USERNAME/Library/Developer/Xcode/Products/com.companyname.Your-App/VERSION/Crashes/
export set DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer
(this should be the location of the "Developer" directory inside of your XCode app bundle).
Locate the symbolicatecrash script: symbolicatecrash knows how to find your symbolicate crash logs using the dsym from step 1. Apple moves it around from version to version of xcode. You can find it like this: find /Applications/Xcode.app/ -name symbolicatecrash. In XCode 8, it is in /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
Backup your crashes folder You may want to backup your crashes folder (/Users/USERNAME/Library/Developer/Xcode/Products/com.companyname.Your-App/VERSION/Crashes/)
Symbolicate all of your crashes: Be sure that you are still in the Crashes directory from step 4 and type
for i in `find . -type f -name \*.crash`; do cat $i | /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash --output $i.sym; mv $i.sym $i; done;
This symbolicates each .crash file into an output file and then copies that back over the original, unsymbolicated file.
View Crashes Return to the crashes organizer and view the symbolicated crashes
I tried to copy symbolicatecrash file from xCode 7.2 and pasted it in xCode 7.3 in the following path:
/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/Current/Resources/
Am using Crasher script to symbolicate the crash reports How to use Crasher
According to the documentation of Xcode 9.0:
The Crashes Organizer symbolicates unsymbolicated logs, if they are
selected, using a local .dSYM indexed by Spotlight. (22550064)
You can check out more on this in Xcode's Documentation.
I need to deploy some in house software along with an extension, e.g. a native messaging app.
Based on this page: https://developer.chrome.com/extensions/external_extensions
It doesn't look like you can install from an external .crx anymore.
I've used the master_preferences file before:
https://support.google.com/chrome/a/answer/188453
But that only works with new installs & I need to deploy to my existing users who are already setup with Chrome.
So is my only options to publish to the Web Store & have my users click on an Inline Installation link?
I have signed an Adobe AIR desktop app using a Cocomo Certificate. When I install on a Mac, the publisher is UNKNOWN. But the same .air file sent to a windows user is OK and installs as any signed app should.
Why should this happen? A certificate working on one OS, but not the other?
How can I investigate further? - to determine the cause.
Here are some more details:
The Certificate was obtained by a colleague on their PC. They converted it to a .pfx file, and sent me the .pfx, along with the password they used. I built the signed air app on my Mac.
My guess is: in addition to the main .p12/.pfx key for the AIR build process, you should try to use Mac Ceritificate (Developer ID Application: http://c2n.me/3qcrChL.png ). It helped me. The certificate might be got on the Apple Developers website: https://developer.apple.com (if you have a subscription).
In my case I was able to install .dmg on my MacBook Pro (where the .dmg file was created), but other users weren't able to install (when I send the file through the Internet or Skype).
Actually, the very process of signing is not clear. In my case I had to go through few steps:
1) Create .dmg (regular Adobe AIR build)
2) Deploy it
3) Sign the folder inside of it, something like dmg-folder-name/Contents/Resources/application-filename/Contents/MacOS/application-filename (where "dmg-folder-name" is sort of combination of the filename of the application + ".app", "application-name" is the filename of your application)
4) Sign the folder dmg-folder-name/Contents/MacOS/dmg-volume-name (where "dmg-volume-name" is something like "Install " + the filename of the application)
5) Sign the main dmg-folder
6) Create the new .dmg based on the signed files
It took a lot of time for me to figure out the correct solution. Also, please, pay attention to the order of steps, because it's IMPORTANT to sign the content of the main folder before you sign the main dmg-folder!
Also, I was able to find the topic on the Adobe website: https://forums.adobe.com/thread/1470113 . It has a lot of suggestions and some of them don't workd in my case, but some of them helped me to find a solution.
I've created and installed all the required certificates as far as I can tell. If I look in the details of the certificates they are all valid.
I've set the config to release in monodevelop.
In the options of MonoDevelop, I've choosen "Sign the application bundle"
In Identity I've choose the "Mac Developer" certificate I created.
I've created a profile which matches the "Profile Bundle" in info.plist.
However, it can't be found by monodevelop in provision : "No matching profile found"
What am I missing?
Really hope somebody knows where I'm going wrong. I'm soooo close to finally getting this stupid app working.
It sounds like you don't have the Provisioning Profile that you created on Apple's Mac Developer site installed on your machine.
If you open Xcode's Organizer window and select the "Devices" tab at the top, there should be a list on the left-hand side of the window with items like:
Library
Provisioning Profiles
Software Images
Device Logs
Screenshots
Select "Provisioning Profiles".
At the bottom of the screen, you should see a 4 buttons: New, Import, Export (on the left), and Refresh (on the far right).
Click the Refresh button and it will query Apple's developer site and download all your Provisioning Profiles.