I've seen solutions like AppHub that allow changes to an already-published iOS App without submitting an updated version to the App Store but as far as I know it doesn't support Xcode. Are there any others that are similar to AppHub that support AppCode and Swift?
My reason behind this is that I am making an app for my school and don't like using WebView. There is an announcements tab that needs to be updated daily but to submit an update to the App Store takes a couple of days.
If you are adding daily news to your app, putting a new version on the App Store every day is definitely not the way to go. Look into a backend service like Firebase or AWS to deliver content updates without the need for the user to update the app daily to see them.
Related
we published App on app store,and it is available to download
after some time we released update for that app,
we know that app has an update available to download
but on App store in upcoming automatic updates list, app store is showing all other apps other than our app.
Is there anything we missed here?
Do we need to change some setting on App store connect?
I am attaching Screen shots of what I am saying
this is Image of upcoming automatic update list
this is image of our app on app store
I am not used to Apple/IOS stuff, but tried to find solutions on google but had no luck with that.
Upcoming updates shows the apps that have opted-in for a 'phased rollout'. If you have opted to roll-out your update to all users at once, you will not see your app under the automatic update list.
Hey all I’m new to the world of Xcode and building apps.
I am wondering if it were possible to have an app run in the background and have it listen to the photos library and if it finds a new photo has been added it would automatically upload that to some type of rest api call without the user having to interact/do it manually?
This will only be used in my household so I’m not looking to get it into the App Store or go through any approval process that apple does if it were going to be in the App Store.
So before I spend too much time looking around - is this possible with iOS 14+? Only thing I have come across that remotely sounds like something that would work would be this PHPhotoLibraryChangeObserver but I’m not sure if the user has to interact with it in order for it to be used or not? I’m open to any suggestions you more experienced Xcode programmers have about the above.
Hi we have an iOS app in itunes which have more than 20,000 downloads.
since we have re-branded our company we have developed a new app which includes extra features than the existing app. New app is with new name and Bundle id.
So now rather than taking out the existing old app, we want to redirect all the existing users to our new app. How can we do that ?
what we did was , we updated the existing app version with the popup, which says this app no longer available please download our latest app. but this got rejected by apple.
Any best practices to decommission an ios app
Thanks
Apple will not allow you to completely drop all of the features in an app - they want users to still be able to use the app. Imagine if all of a sudden Facebook make it so no one could use their app, and forced everyone to download a new app. It probably wouldn't turn out too good for them.
What you should do is just make an update to the old app. All of the users will be able to update easily, with no hassle, and you won't lose and users.
Another way to do this is by calling your new app MyAppName 2, although this will really only look good if you're developing a game.
If you would really like to get rid of your old app, I would recommend removing it from the app store and contacting Apple (You'll have to give them a good reason. Wanting people to pay for a new app doesn't count as one)
What many developers do, is add code to an app that checks a specified endpoint for instructions at each launch. The instructions are either, run as usual or, display this message and URL.
Personally, I would do this, and also update the old app as a freebie teaser for the new app. Apple pays less attention to reductions in functionality than they do to "kills".
Run the teaser for a year or so, then kill it.
We are ready to start the development of an using trigger.io, however some last minute external feedback pretends that trigger.io apps are systematically being rejected by Apple since the launch of their new Reload system (which pushes updated HTML/CSS/JS code without having to re-sublit to Apple for app updates).
The only reply regarding this topic on stackoverflow (Apple App Store ok with Trigger Reload?) was issued by one of the founders of Trigger.io, so I'm really looking for some totally independent feedback on this.
Can anyone provide any real-life feedback on this ? Has anyone ever succesfully submitted an app to the store ?
Trigger.io's page https://trigger.io/examples/ provides very few examples of submitted apps, so it isn't very convincing either...
Any feedback greatly appreciated !
At Hojoki, we're successfully submitting an app built on Trigger.io to the App Store for over a year now. We're actively using Reload (e.g. pushed reloads to all our iOS users three times in April) and never experienced any issues regarding approval and Reload.
There were two times that the app has been rejected (related to meta data stuff..), however this had nothing to do with Reload or Trigger.io at all.
The only Reload-related app store rejection we know of happened on May 9th (six days ago). This was due to Reload files not being marked as exempt from iCloud and iTunes backups.
There are loads of apps using Reload live in the app store, so it's not a general problem - it's just that this particular app was using Reload to distribute >100MB files.
Nevertheless, v1.4.46 of the Trigger.io platform contains a fix which sets the no-backup flag, to be extra safe.
I need to submit to the Apple app store a new version of my app. My app is based on JSON feeds. The problem is that the new app works with a new version of the feeds, but the new version of the feeds can't be released while the current feeds still working for the current app.
So my question is how apple can review my app? Will Apple approve my app even if the feeds are not live?
My idea was to submit the app for the review even if it's not working, and if is approved start the new feed and remove the old one. Any suggestion on how to solve this problem?
Another idea could be submit the app, and while is in queue keep the old feed live, and after 4 days start the new feed (so Apple can review the app), in this case the app won't work just for a couple of days.
Thanks
Francesco
Short answer: No, your app will be rejected.
Longer answer:
You should provide a way to keep the current (past version) feed working at least for a while along side the new one, otherwise people that don't update the app, which you have no way to control, will have an application that doesn't work.
What you could/should do is keep the previous version available on one url (yourhost.com/feed) and the new version on another url (yourhost.com/feed/v2/).
Internally you can keep just one version, the newer, and then use some kind of facade/converter to handle the conversion from the new schema to the old one. This way you would only need to maintain one version of the code while providing a way for both versions of the application to work.
Your app will be rejected if Apple tester find it empty of content.
I've had an app rejected for "not being ready for production" for something very similar.