Xcode 7.0 beta / IOS9 / WatchOS 2 - no symbols for paired Apple Watch? - apple-watch

I got this message within Xcode, any idea how to fix it?

From https://forums.developer.apple.com/thread/3380:
Xcode failed to download the symbol files from
http://adcdownload.apple.com/Developer_Tools/watchOS_13S5255d/Watch1_1_13S5255d.dmg.
I was successful to launch my watchOS app by following steps.
Download the symbol file installer for 13S5255c from http://adcdownload.apple.com/Developer_Tools/watchOS_13S5255c/Watch1_1_13S5255c.dmg.
Create directory "~/Library/Developer/Xcode/watchOS DeviceSupport/2.0 (13S5255d)/Symbols"
Mount the DMG and open Watch1,1.pkg.
Change the destination directory to above directory. (DO NOT install to default location! OS X will be destroyed!)
Install symbol files.
Open project on Xcode 7 beta.
Disconnect and connect iPhone.

in case anyone is still struggling with this, i was able to solve by updating to the most recent version of xcode.
everything was working until watchos 2 beta 5 installed on my watch, then i got this error. updating to xcode 7 beta 5 allowed my watch to appropriately have the new symbols installed.

The solution that worked for me is based on the earlier post, but to simplify things I’ve followed the initial steps, changed the directory name to work with Beta 5 and zipped the relevant folders. So the simplified version for Beta 5 is:
Download the zip file from here to the target directory: ~/Users/[user]/Library/Developer/Xcode
Unzip the file. You should see a new folder named “WatchOS DeviceSupport” under your Xcode folder, with another folder named “2.0 (13S5325c)”.
Open project on Xcode 7 beta.
Disconnect and connect your iPhone.
That’s all – it worked for me, I hope it will work for you as well.
I couldn't post the image, you can find the complete post here.

Related

Unable to open Xcode 10.1. Getting Package Authoring Error

There are two Xcode 10.1 and 11 installed on my Mac wherein 10.1 is default one. I was able to open project using Xcode 10.1 until few hours ago. However, after restarting my mac I'm facing strange issue as described below:
Package Authoring Error: PackageInfo bundle reference found without top-level bundle definition. Bundle will be skipped.
Check attached screenshot for additional details.
Below are solutions that I tried:
Tried mutiple time to open project using Xcode10.1 but still the same issue
Restart Mac.
Take a note that I cannot move my project into Xcode11 there are certain dependicies due to which I've to use Xcode10.1.
Apple is enforcing developer to use latest version of Xcode.
There are two solution for this:
Move on to Xcode 11 (recommended)
Delete Xcode 10.1 and freshly install Xcode 10.1
I would suggest to go with solution 1.
I have read somewhere answer but I am not able to get that link here,
but I know that you can try, change the system date to 3rd October 2019 and try again so it will work.
This is not my answer so all credit goes to unknown developer.

Xcode SDK Version Issue

I'm having a bit of an issue with distributing an app via the latest version of Xcode (Version 10.1 (10B61)). Every time I try to upload it to the App Store via organizer, I get this error after uploading:
WARNING ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.0 SDK. 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."
Previous answers to this question said that it was just a warning and that I should still be able to upload my app, but it is now March and I am still getting the error even on 10.1. iTunesConnect will not let me select these builds and I get emails about the validation failure.
Further details:
-The app is an iMessage extension, and uses exactly 1 framework from Carthage, which is up to date with the latest framework version and Carthage version.
-My project and Message extension targets Swift Language Version build setting is Swift 4.2.
-My deployment target is iOS 11.0, but the issue persists after selecting iOS 12.1.
-The app compiles and runs fine on my physical device running iOS 12.1.
-The issue persists after a build folder clean.
-The issue persists after reinstalling Xcode.
If anyone has any suggestions as to how I can verify my app is compiling with the latest SDK please let me know.
Whether the app runs on given iOS version, has no relevance to which SDK are you really using. The definitive SDK version used for building is found in the app's Info.plist.
after Archiving, Show the xcarchive in Finder.
right-click, Show Package Contents.
open Products/Applications/YourApp.app
right-click, Show Package Contents.
copy the Info.plist to some place where you can run terminal commands on it
/usr/libexec/PlistBuddy -c "print :DTSDKBuild" Info.plist
You would expect it to show "16B91" for SDK 12.1. If it's something else (SDK 12.0 would be "16A366"), here are some ideas:
inspect the Carthage dependency. Are you really building it locally or downloading a prebuilt binary? If in doubt, force local building with --no-use-binaries. Remove whole Carthage folder (Checkouts as well as Build) and start from scratch.
rm -rf ~/Library/Developer/Xcode/DerivedData instead of just "build folder clean"
Verify MacOS System Report section Software/Developer for the actual SDK versions that MacOS thinks that you have
xcode-select -p to verify that you are really using the Xcode instance that you would like to
If all looks correct on your side, fill Technical Support Incident. Report the exact rejected build which you uploaded already. That should speed up the support reaction.
I filled out a bug report with Apple because I was experiencing the exact same issue and none of the above solutions worked. They made a change on their backend and now everything is back to proper working order.
If you haven't tried in awhile, make another attempt and I'm betting that it'll work this time.
I was having the same problem. My app was compiled in Xcode 10.1 but I was still getting the SDK warning. I was able to resolve it by doing the following. I'm not sure if all these steps are necessary. I didn't try validating between steps.
I upgraded macOS to Mojave (10.14.3). I had been running High Sierra.
Delete Xcode from applications folder
Reinstall Xcode from the app store
Open my project and run Project->Clean Build folder
Archive and upload and no more warnings

Cannot find location of realease file

I've recently upgraded my XCode to 4.3.2 and also my OS to Lion so that my apps can work with IOS 5.1 plus. I'm now trying to upgrade a couple of old apps and I can't find where the app files are to upload to Apple.
The strange thing is that I can use Terminal to locate where my DerivedData folder is but when I try to use Finder the Library folder does not exist. Is there anything I am missing because Xcode tells me the path to me build file is /Users/SC/Library/Developer/XCode/DerivedData/MyAppFolder/... but I cannot find it when using Finder. When I use Finder the Library folder does not appear even though it shows up when I use Terminal.
After you build and archive in XCode 4, you can go to Window>Organizer>Archives to view all your builds. You can validate and submit any build from there or right click and choose 'Show in Finder' to locate the app.
Ps. See my comment regarding the user library in Lion

Xcode 3 wont allow me to Install Xcode toolset

So I attempted at giving Xcode 4 a swing, after uninstalled XCode 3, and it failed me.With all the shortcuts out of place i didn't feel at home. So i uninstalled XCode 4, and began installing Xcode 3 once again. but this time. I am no longer allowed to download the Xcode Toolset.!
http://tinypic.com/r/29z242d/7
At first i assumed that the Xcode toolset would someone works it way into the instillation and it would all work out. but after installing this more that 3x on my computer I cannot seem to FIND XCODE at ALL! nor can i find iOS simulator or any other software. What do i have to do inorder to fix this?
I think this is happening because I inappropriately uninstalled Xcode 3 the first time, I used an application called App Zapper rather than running the -sudeo command...
You can install Xcode 3 on Lion using the following method:
Mount the Xcode 3.2.6 DMG
Open Terminal
Enter the commands:
export COMMAND_LINE_INSTALL=1
open "/Volumes/Xcode and iOS SDK/Xcode and iOS SDK.mpkg"
Use at your own risk as Xcode 3 is not supported by Apple on OSX Lion.
If you are installing alongside Xcode 4, make sure to install into a different directory (create this in Finder first), and then you can untick all the boxes apart from the Essentials and it'll run just fine.
Source: http://anatomicwax.tumblr.com/post/8064949186/installing-xcode-3-2-6-on-lion-redux
Just a heads-up: on Mountain Lion and Mavericks (and quite possibly on other versions as well, but I only "tested" this two...) this causes a kernel panic at startup, so I would advise against installing Xcode 3 on them.
If you already did that, and need some help, here and here are some information.

what's the issue with this application deployment in iOS4.1?

When we gave our app for ad-hoc testing, our tester reported that the app could not be installed because iTunes gave the error "resources have been modified". Please note that the app installed fine previously with the same procedures which we implement for deploying apps during ad-hoc. The only difference is that the device used for testing has its OS upgraded from 4.0 to 4.1 and now we are unable to install the app.
There are no issues with the zipped application file sent, no Thumbs.db file is present to corrupt the .app folder and all the distribution profiles are in place.
Also, we found out that the base SDK for building this app is 3.0, which installs fine in iOS 3.1.3 and 4.0 but gives issues with 4.1
One other app which has been written with base SDK 3.1.3 deploys correctly in iOS 4.1 though.
Please suggest some workarounds for this deployment issue
This is because someone has modified the files in the .app folder. If people go into the .app folder Thumbs.db will be created automatically, or they may have modified/changed something else.
Try rebuilding the file and zip it into a folder called "Payload.zip" then change this name to "yourAppName.ipa". This will stop people from being able to modify the files in the .app folder.