When trying to publish a new version of the Appcelerator Arrow application, I get the following error
ERROR | App {MyArrowApp} has been published 10 (maximum) versions.
There is no documentation on Appcelerator about such a restriction anywhere, so I'm stumped! That said, how do I delete the old versions to get around this problem - I don't care for prior versions to be maintained except for the active one?
Please note that I have a paid subscription to the Appcelerator Arrow platform, so this is even more surprising.
As per Appcelerator Support (refreshingly helpful):
Please read the following sections:
--delete_oldest
--list_versions
http://docs.appcelerator.com/platform/latest/#!/guide/Arrow_Cloud_Command-Line_Interface_Reference-section-43299782_ArrowCloudCommand-LineInterfaceReference-publish
Related
Just showing the Documentation Window crashes XCode 12 (cmd-shit-0) - anytime I do it.
Does anybody have the same problem, an explanation or a work around ?
Update: There's now a new version (12.0.1) in the App Store that fixes this issue.
I'm experiencing the same when using the version from the App Store. People in this Apple Forums thread are reporting that it doesn't occur with the GM download from Apple's developer resources, despite the build identifiers being exactly the same.
Anecdotally, I can confirm that I was able to use documentation in the GM version before I deleted it in favor of the App Store version. So this may in fact be a viable workaround until the App Store version is fixed.
The Xcode on the app store is some sort of unknown version, (Since there it release even before the GM version available). So get rid of it and Download The Xcode From The developer.apple.com or click the proper version below. Then it. will work like a charm.
This needs you. to login to your account
Don't forget to remove the appstore version downloaded Xcode
Direct Download
Xcode 12
Xcode 12.2 Beta
I use xcode 12 beta 5 works well can open document window, when I upgrade to GM seed, it can not open document window any more. When I fallback to xcode 12 beta ,open document it crash every time. All these happened on mbp13 pro, but my another mbp 15 with the same macos version works very well.
I guess it have something with macOS system, not xcode version.
Now I upgrade xcode by AppStore ,crash all the same.
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?
I have an app that contains a Today Widget and it's working fine during debug as well as the first version distributed using TestFlight & HockeyApp.
The problem occurs when the user updates to a newer build through their service. The widget seems to just show the snapshot and never actually initializes (I print out logs when it gets to certain parts of my view controller but I'm not seeing those).
To fix this problem the user will have to restart their device or delete and install the app again.
Does anyone know of this issue and/or how to fix this?
I've seen the same issue using OTA installation (Testflight web, HockeyApp) but it seems to work fine distributing through the new Apple Testflight app.
I would suggest filing a radar ticket to Apple if you plan to continue distributing apps with widgets through OTA methods. Personally I've just switched over to using the new Apple Testflight app to distribute my betas.
When ready to present an app to put on the appStore; is there a minimum version of Xcode required? Or any version however old is good?
Thanks
According to Apple,
You should always use the latest Xcode (requires Apple ID to login)
Note: You can build with the very latest SDK, and run your app on an earlier operating system. The Deployment Target build setting controls the lowest operating system version that your app will run on. This setting is independent of the Base SDK build setting.
Using any other SDK is TEMPORARY
It's important to understand that using an older SDK is a temporary workaround, not a solution. Issues preventing your app from using the latest SDK should be fixed as soon as possible. It will be much easier to fix these issues while the older build system is still supported.
Latest & Easiest way
Application Loader
You need to have some minimum version of the XCode, but no need to have the very latest one...
And for easy steps & guidelines to submit app in to appstore please check out the following url
Easy Steps for App Store Submission & Certificates creation - By iOSCodeGUIDE
There is a nasty bug in IOS 4.2 having to do with the tint color of the navigation bar in a split view controller.
I have the 4.2 sdk on my mac, is there a way to install 4.0 on top of it and have them both work?
The relevant SDKs live in:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs, and
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs
In the past I've been able to keep an SDK from a previous version by simply copying the relevant folder forwards. Xcode simply spotted the old SDK and continued offering it as a Base SDK. So you'd need to install the old SDK somewhere, keep hold of the relevant iPhoneOS4.0.sdk and iPhoneSimulator4.0.sdk folders, install the new SDK and then copy the backed up folders in. If you use Time Machine, you may even be able to grab them directly from there.
However, I believe this to be an unsupported way of proceeding, so it's not necessarily guaranteed to work. And all the usual warnings about doing anything Apple don't support apply.