I just (re)installed the Fabric app for macOS yesterday. This morning I receive a notification that there is a new version of the Fabric app for Mac. My version was 2.6.17. I downloaded Fabric again this morning and its version is ... 2.6.17.
I guess it isn't a big deal reinstalling the same version of the Fabric app every now and again (it takes almost no time), but it would still be nice to know what the current version available for download is prior to actually downloading and installing it. And won't the app itself ask me to update it if it truly needs to be updated?
Thanks for letting me know. Usually this means the app cache had an issue. It should now be reset, but you can manually do this as well by running:
rm -rf ~/Library/Caches/com.crashlytics.mac
Related
I released an iOS + Mac Catalyst app that uses Core Data and NSPersistentCloudKitContainer.
No issues for the users, but something is wrong for me when installing the app from the Mac App Store: it not only uses the development database instead of the production database, but also merged both (I think it loaded the dev one from local storage and imported the prod one from iCloud).
I once had something similar on iOS too but it was easy to fix: delete the app installed by Xcode or TestFlight, then install via App Store.
However, I can't find a solution for macOS. I've deleted the app's folder in ~/Library/Containers and deleted the app from /Applications but after re-installing from the App Store, it happens again.
What can I do to fix this?
Note that I've found this answer but it's not exactly the same - in my case the released app is using the development database instead of the production database on macOS, so I can't do the "if DEBUG" thing (unless I first clean everything maybe and do this for the next version?).
Could not locate device support files.
This iPhone 5s (Model A1457, A1518, A1528, A1530) is running iOS 10.3.1 (14E304), which may not be supported by this version of Xcode.
You need to update Xcode whenever the iOS version you want to work with is higher than the highest version that Xcode's simulator has installed. This can be done one of two ways. The simplest is to use the App Store to download/update Xcode. If the App Store doesn't show any updates, you must manually download the latest Xcode build from https://developer.apple.com/.
You will need to manually download from the Developer portal when the version of Xcode on your computer was downloaded there previously. For example, many beta testers may download the file directly instead of using the Mac App Store, since it is a beta download.
I would recommend trying to keep updates done through the App Store by downloading Xcode from there initially. The benefit to this is that it can automatically update as well as save space on your computer (Xcode is a big file, and you may not have enough space to download a new version if you still have the old version).
As of the comments, I will now write an answer. :-)
Whenever you encounter this error there might be two reasons for that:
The OS version is too old
The iPhone's/iPad's OS is too new for your Xcode version
If it is too old, you may need to download older SDKs and OS versions.
You can do so in Xcode. Go to "Preferences" -> "Components" and download the appropriate Simulator.
If the devices OS is up to date, you have to make sure your Xcode is also up to date.
Either you update Xcode through the AppStore OR (and I prefer this way, as the AppStore is used to hang up in a certain state and cannot be completed any longer until you restart the Mac, at least I had this several times).
Side note: Xcode requires multiple GB of free storage. Make sure you have enough free storage left for an update.
You can download the latest Xcode version from the https://developer.apple.com portal:
Go to Downloads:
And then select the item of interest (in your case Xcode)
Trying to download Xcode 7.3.1 but download process is stuck for atleast 1 - 1/2 hour, is it stuck, is it going to complete? I have latest Mac OS installed
Tried solution provided on this link but non worked
XCode 7.3.1 Update Not Installing
It always happens to me (Well, not always but it happens, and also with another apps). What I do is to delete the Xcode app, and then install it again from the App Store or from the Developer's site.
just install the new version of Xcode (7.2.1), he took a little longer than expected.
But when it finished and run the xcode continues with version 7.1.1
I thought it would be solved by restarting the Mac, but no.
Any idea what can be spent? or happened to me to be done?
!EDITED!
My MAC version.
My xcode options
My applications
I had exactly the same problem. I installed 4GB large 7.2.1 version of Xcode from the AppStore over an existing 7.2 version, and whichever way I was launching Xcode it was always the same old 7.2 popping up. What was worse I could not download 7.2.1 again, as AppStore app was not showing Install button anymore, but rather Launch button instead (like it was installed).
Finally I found a solution. I went to Downloads for Apple Developers site (a login to a developer account was required), I dowloaded Xcode_7.2.1.dmg 4.7GB large from there, launched an installation... which successfully replaced the older 7.2 version of Xcode.
Another answer suggests installing Xcode via a Developer Member Center download. I'd like to caution against this, and suggest an alternative approach.
Shortly before Xcode 7 became available, I upgraded an Xcode 6 installation to 6.4 by using the download. I did this to save download time for upgrading multiple machines (I put the installer on a flash drive). I subsequently discovered that using the downloaded installer broke tracking the version history in the App Store, and I was no longer able to upgrade via the App Store. Also, I was no longer notified of pending Xcode updates via the MAS "Updates" panel.
So a possible consequence for you may be that the App Store may not be able to handle your future Xcode updates, or even notify you when an update is pending.
What I ended up doing was deleting my then-current Xcode installation (I used AppDelete to get all of the components of the installation), and starting from scratch using the App Store. I recommend doing the same. Probably the best way to start is to try deleting Xcode via Launchpad. But if that doesn't work (say, it doesn't delete all versions if you still have multiple versions), try AppDelete or a similar app.
I should note that one reason I used the download to upgrade Xcode 6 was that I'd done so previously without breaking the App Store's ability to track Xcode's version history. Whether that previous behavior was a fluke, or whether the later behavior (losing the version history) was a fluke, I can't say.
If you've already installed via the Member Center installer, you can check to see if you'll have this problem by looking up Xcode in MAS. If the store shows you have the version you manually installed, then all is well (probably!). If not, either you'll have to keep track of updates by yourself, or you should re-establish MAS version tracking by deleting Xcode and starting from scratch via MAS. I'd be interested to learn whether the store is tracking your manual installation.
I removed the embedded app extension for my watch app, and the target dependency so that my app would discontinue support for the apple watch.
The app never quite worked, and the more my app evolves the less the apple watch does for the user.
After removing these things I attempted to install the build on my phone. It never was able to do so, until I deleted it.
I tested this using testflight.
The app won't install. It downloads, then sits at about 90%. Will NOT update
How then am I to remove support for the apple watch????
This answer may seem weird as it does not have to do with apple watch at all, but I have had the issue you've had with installs not finishing before. I was really stumped as to what it could be, looking into all of my extensions as you are doing now.
It ended up being that I had placed leading zeros in the version number/build number.
For example: Version 4.01
Instead of: Version 4.1
For some reason this caused the error you described for me. Can you confirm you don't have any leading zeros?