Maybe that's a stupid question, but how do I download an owncloud app which is not approved yet?
Precisely, I want to test this:
http://apps.owncloud.com/content/show.php/AppVNCZimbra?content=155100
and it says there were already 661 downloads but I cannot find a download link nor any information on the owncloud website how to download it or why I cannot download it. There is one post in their forum of a guy asking the same question a few months ago but no one answered.
The app is under review for days and who knows how long the review might take.
An ownCloud app currently marked as "nor approved" is in review process stage. That probably means it could be downloaded before, but some details was changed (most likely an update). Because of this change the app has to be reviewed again to make sure no backdoors or security problems were introduced with the update.
During the review process only members of ownclouds review team can access the app. As soon as it has been approved you will see the download link again.
Related
My employer has a free iOS app in iTunesConnect that was originally released a couple of years ago and has received various updates over time. They now wish to stop supporting older versions of the application (1.x) and disable these older versions of the app.
My questions are:
Can we stop users from re-installing old versions of the app? If yes, how?
How do we disable/remove old versions of the app in iTunesConnect?
What is Apple's policy regarding disabling/removing old versions of applications?
I'm not an iOS developer and am unfamiliar with the whole Apple application development process. I have searched the web as well as the Apple developer centre and I've read through the Apple Developer Program Terms and Conditions but I haven't been able to find answers to any of my questions.
I have managed to find information about removing an application from sale but this removes the entire application, rather than just specific versions. (Deleting a free app from iTunesConnect)
David Smith's article (http://david-smith.org/blog/2012/06/20/hacking-paid-upgrades/) on Paid Upgrades mentions the ability to provide fixes for previous versions if they're not deleted from iTunesConnect. When I log into iTunesConnect, I only see the current version of the app listed so I'm assuming prior versions have been deleted already. I would, however, like to confirm that users can no longer download old versions of the app.
This article mentions users being able to download old versions of apps from iCloud (http://www.macrumors.com/2011/06/09/icloud-supports-re-downloading-some-discontinued-apps/) - can we prevent this? One option would be to mark the the version as having a "legal issue" but what ramifications does this have? and if I can't see the app in iTunesConnect then how do I do it?
I found a post asking about how to force a user to upgrade the application every time a new version is released but this doesn't answer my questions either. We want the users to upgrade but we're not wanting to force it programmatically. (Can I force an iPhone user to upgrade an application?)
I've also found lots of posts asking how to revert to previous versions of an app in the app store but again, this is not what we're wanting to do. We're wanting to disable older versions of the app but leave the most recent versions alone.
Before the flame wars begin:
Users that are unable to update to the latest version of the app for whatever reason are able to use a mobile website in place of the app. The website has the exact same functionality.
Can answers please be kept on-topic rather than getting into great debates over whether one should/shouldn't maintain legacy versions.
Thanks in advance :)
Users can typically only ever download the latest version of an application. There are a few ways I think they can get around that but in general only the latest version is available to users via the normal means.
If, however, you absolutely must prevent the old versions from being released you can do so when submitting a new update. Right after you say "Ready for Upload" you will be asked a question about if this update was for a 'legal reason' if you click YES then you will be given the opportunity to disable old versions of the app from download.
As to Apple's policy on this...I have no idea. But I can't think of any policy that would require you to support older versions moving forward.
I'm getting ready to submit an App that relies on the user being at specific locations to watch a video. (Kind of a mashup of geocaching and youtube.) Needless to say none of these videos are anyway near Apples headquarters. So how will the App store review people be able to properly review the App? Do I have to provide test data in their vicinity or can I instruct them to fake their geolocation to a location that works?
I guess the best way is to just submit it once, wait ~7 days and see what they have to say,
but since they have special toolchains to test apps, it shouldn't be a problem.
Just make sure to mention it in the review notes.
I've submitted an update to an app once that requires an user and password to login, and gave them a test user. When I checked the server logs, they never logged in once - but the app was still approved.
The iOS Simulator can 'fake' its location :) Though I doubt what they DO review in their process, because once they accepted one of my Apps' update which crashed upon launch...
Recently had to deal with this myself... submitted a location specific app without any extra review notes, and the app got rejected. In the rejection notice I was given the instruction to create a video of the app in action and then provide a link in the review notes.
So I used another iPhone to take the video, put some basic explanation text in the video using iMovie, uploaded to YouTube, put the link in the reviewers notes, re-submitted the app and then 5 or so days later it was approved.
As I understand, they review team does NOT test the usability nor stability of your app during app reviewing. All you need to do, is to provide an testing account, and some sample data, screenshots to them helping understand how your app works. If the app does not show any data because of a reasonable circumstance, it's not the problem of your app quality nor user usage, but data coverage. So you won't have problem with it.
I have made multiple simple but fun apps for iPhone in the past few months and have had them rejected by Apple during the approval process.
I have put many weeks or months of effort in some cases. I just hate to have these apps go to waste without anyone downloading them.
Since those apps of mine are never going to see the light of the day on the App Store, is there a way I can let family and friends download those apps if I host those binaries on my website? Can anyone tell me the process or walk through instructions?
Are they simple enough that if I post them on Facebook most average users are going to get it? Is there already a website out there that lets users like me (with unapproved apps) to host those files for everyone in the world to download them?
Have a look to testflight.
You just need an email that can be accessed on the iPhone and add the specific user to test flight, once he is register you can get the iPhone id and add it to the provisioning profile.
When you create the build and upload it , the users are notified by email and the app is installed remotely by a few clicks.
You can authorize a limited number of users to test your app through ad hoc provisioning. The free service provided by http://www.testflightapp.com makes the over-the-air distribution and provisioning process fairly simple.
You might find these links useful
http://jeffreysambells.com/posts/2010/06/22/ios-wireless-app-distribution/
https://testflightapp.com/
Good luck
Harv
Why not just open-source them? You’re probably not going to make a lot of money distributing them with TestFlight or even Cydia. Instead, clean the code up to remove any proprietary things you don’t want to include (API keys, etc.) and put it on GitHub. Not only will this help the community, but you can use your GitHub account as a kind of résumé for future employers or clients. What’s more, you might even get free help with your code if someone forks your game and makes changes!
Old thread but could Enterprise developer's license help here, as long as you are not selling them apps?
Just a thought.
Can someone provide concrete info on how the app upgrade process works on iOS as far as the developer is concerned? I've been rummaging through Stackoverflow only to find hand-waving explanations and no links to official documentation. Google search results only led to Cisco's IOS and the end-user upgrade process. I'd like to know the following:
How does the App Store know when you've provided a new version? Do I have to implement something in my app, which the App Store pings? Or do I set things up stuff through the Apple Developer website? I've been waiting 2 months for developer approval and have no idea what's going on behind those doors because I get access-denied messages when trying to read official articles.
Is there any Objective-C code I need to write for an upgrade to be possible? Any plist I need to edit?
How is payment affected when version 1 of the app is free, then version 2 is paid or version 1 is paid and version 2 changes its price.
Does Apple allow me to do forced upgrades? All the answers on Stackoverflow have been, "I think this is bad business logic" or "I think Apple forbids this, but I don't have the official documentation to prove it." At a certain point, very old versions will be too time consuming to support. You don't see Microsoft still supporting Windows 95, do you?
You just submit the new version to Apple. When it's approved, it will appear in the App Store.
Same as above, Apple pretty much does it all for you.
If you transition from free to paid, everyone that has downloaded the app for free will not have to pay to upgrade to the paid version.
IIRC you cannot force users to upgrade, but you can display a notification within the app to alert users that an update is available. To implement this, I would just have the app request a file on your server that tells the app what the current version number is. You do not need to support users on old version, if they have problems with an old version, it's fine to tell them to upgrade.
I have been looking around for an answer for a specific question but just got hints for it here and there. I want to know when i submit an app for review for the AppStore:
First, how long does the review process usually take? I know that it may vary but just want to have rough estimate if possible
Second, when an app is accepted does it go automatically to the app store or the developer has the control over when to release it there?
Cheers
AF
check out details, which is my recent app on appstore,
It take 1 week for approval , As I remember, it was taken 3 days too once.
Time taken to publish is all in their hand.
App will be publish directly to appstore.
But you can remember the option for publish by you or apple :) at the time of submitting app
From my experience review takes about 2 weeks recently, but it varied from 2 days to about a month in the past.
When you submit an application you have an option - whether to make application available on appstore immediately after it was approved by Apple, or hold it before developer does that manually, so if you did not select that option then Application should be published on Appstore by default. (See pages 75-76 in iTunesConnect Guide (warning - large pdf file here))