If I sign an application with a legit developer license, is it possible to install some developer preview of it into an iOS device without jailbreaking it?
Saw some similar questions, but they didn't clearly answer this question for me.
Just to get this question solved, I am adding my comment as an answer.
See questions like Showing beta versions of an app to a customer.
The keyword you want to look out for is
AdHoc Distribution
The basic procedure involves adding the UDID's of your test-devices to your developer account and enable them for your test-app's.
For details on this procedure you may also check Apple's documentation on the subject Distributing Applications
Related
After making an update to an iPad app I released some time ago, I've been getting reports that people are unable to actually update the app without deleting and re-installing. However, as far as I know, nothing in the update should be causing this. (All the update deals with is letting people email PDF documents, nothing major.) When people attempt to update, they're asked for their iTunes password, but after entering it, it merely goes back to the update screen and nothing happens. Additionally, it would seem that this only happens with my app, the people in question aren't having any issues with the other various apps on the App Store. Does anyone know what might be causing this and how I could fix it?
Thanks in advance!
(Also, if it matters, the app is a custom B2B app, the general public can't purchase it.)
I'm removing the text of my answer because it's so inaccurate it's embarrassing. I mistook "B2B" for "Enterprise" and answered based off of that. To make up for it, I'll look into the problem a bit more and if I find anything I will edit this answer accordingly.
Edit:
Okay, I can see why you put a bounty for this question on SO; there's not really any data on a problem like this anywhere. Frankly, there's not much available information on B2B in general. I'll post what I found anyway, in case it can be of any help to you.
I found the details reason behind Maggie's question, there. Per Editing and Updating App Information:
Updates keep the same Apple ID and bundle ID, which means they are
associated with your first version and free to your customers
Also, apparently, "You can't change the CFBundleIdentifier of a released app if you want to release updates for it, the App Store will automatically reject it when you upload." which is something I can vouch for, having experienced this with a normal app. I do know that for a B2B app you do have to submit it to Apple for review, but I can't tell from the documentation I found if you need to actually submit it to the App Store, so it may not go through the various checks that normal apps go through, so this could be your problem.
Aside from that, according to the VPP guide, if your customers are installing the apps on the devices with Apple Configurator (broken right now, per app store reviews) the updates also have to be done with the Configurator. You haven't said that Configurator was involved, but I did find this tidbit.
• Use Apple Configurator to install apps on new or supervised devices.
Apple Configurator on a Mac makes it easy to mass configure and deploy
devices that are centrally controlled. Redemption code spreadsheets
acquired through the Volume Purchase Program can be imported by Apple
Configurator, tracking the number of apps installed on each device. To
update deployed apps using Apple Configurator, you must reconnect to
the same Mac from which the apps were installed. Learn more at
itunes.apple.com/us/app/apple-configurator
Anyway, good luck. Wish I could be more help.
What you are describing (assuming that it is accurate) would certainly be a bug on Apple's side. If users are trying to update the app and the update is not being processed, then in one way or another that is a bug that Apple needs to address. Nothing that you do as a developer should be able to cause that situation to happen. I would suggest contacting Apple and possibly filing a bug report.
It seems that apple wants you to develop the Iphone apps in the latest build. Sometimes this cause issues between realeases (diferent versions of Itunes, OSX, IOS, etc) when you try to update your apps.
Try to publish the app in the latest version of xcode.
That happens a lot in iphone development testing.
Hope this help.
When updating an app, iOS looks for the bundleId and if there is another app with the same bundleId, it updates the app with the highest version number. Maybe the version number is not set correctly or maybe people have issues because an other app (from the AppStore or an other B2B app) have the same bundleID but a higher version number.
I'm by far not an iPhone expert, but it seems something related might have been fixed in iOS 6.0.1.
Fixes a bug that prevents iPhone 5 from installing software updates
wirelessly over the air
I have an app in Cydia and I want to make the same application but LITE version and put it in AppStore. My question is will Apple reject my app if the check it some how. Actuality my app work with web services so I have real worked domain. And I want to use the same domain or to make another second lite-like domain of the original one...
Thank's in advance..
No, the yxflash team does a similar thing, they have a version of their application in Cydia (because, when they released it, the code was using private APIs), and they have another version (actually 3) in the AppStore called yxplayer. So from what I see there, you should be fine, apple doesn't seem to check those things.
This is an explicit violation of the iOS developer agreement; your presence in the App Store will depend on being obscure enough that Apple doesn't notice what you're doing and nobody tells them. That's not how I would want to do business, but to each their own?
7.3 No Other Distribution Authorized Under this Agreement
Except for the distribution of freely available Licensed Applications and the distribution of Applications for use on Registered Devices as set forth in Sections 7.1 and 7.2 above, no other distribution of programs or applications developed using the Apple Software is authorized or permitted hereunder. In the absence of a separate agreement with Apple, You agree not to distribute Your Application to third parties via other distribution methods or to enable or permit others to do so.
Just submit the app, you will be fine.
Apple simply can't prove that YOU also submit the same app to Cydia.
That is, you can claim that your dog/cat/fish/wife/kid used the code to submit to Cydia during your sleep
I have an iPad which has a developer profile enabled and I've been developing apps on it. I got the developer profile from a university program (from the iOS programming class that i took).
Now I would like to return the iPad I already own and would like to purchase a new one. I can't get a new developer profile from the university program anymore as the class has ended a long time ago.
Is there any solution to my situation other than jailbreaking/paying 99 bucks?
I think that you could to write to support of apple. They must to get you right answer. But you can pay 99 dollars, if that not so much for you.
Because the profile is linked to your devices specific UDID that is unique to your current devices hardware even if you did copy the profile it would not work. There are some tutorials online to disable code signing by editing the backup file and restoring this worked for me in the past, but I do not know about the new firmwares. I could register your UDID and give you a new profile if you would like (for $5) you would not be able to put your apps on the AppStore though. Other than that your option is to jailbreak.
I'm talking with a client who is abroad and I'm wondering whether I will be able to send him versions of the iPad app for testing before it's on iTunes.
Is there a solution (e.g. Ad-Hoc?) I could rely that doesn't require jailbreak or anything?
If so, could you please provide me with a link to a guide?
Thank you !
Yes Ad-hoc is what you need, basically you will need to associate your client device identifier (UDID) to a certificate that you will use to sign application.
This is a standard procedure (no jailbreak required) that is fully documented on Apple provisioning portal in User Program Guide (you have to apply ($99) for the developer program and be logged to access this... and it is limited to 100 devices)
Another good thing is to use an "Ad-Hoc" updater such as HockeyKit to ease your client updates and installation procedure...
Yes, indeed, there is an ad-hoc distribution method:
here is its mention on the Apple Developer website. As far as details, I think you have to be in the developer program in order to get direct documentation for that, and sadly I allowed my developer account to lapse. A few key points can be found here
Essentially, you can distribute to up to 100 other iOS users who have your group's apple developer credentials installed on their phone, and the app will remain live for 90 days
Essentially, it's the same headache on the remote side with certs, keys, etc... that you have to do with XCode when developing on the device, but you can put the app on a website somewhere where the remote party can install it on their phone.
EDIT: I found this guide that is presented on a forum if you want to look through the steps.
I have a C# application which needs to be ported to several Smartphones. Monotouch looks like the best choice for the IPhone, if there wasn't section 3.1.3 in the new developer agreeement.
Now the Monotouch website lists 3 Monotouch apps that were allowed to the App store after the new agreement was put in place. Was it just pure luck for their developers, or is Apple actually not enforcing section 3.1.3 except with regards to Flash applications?
Thanks,
Adrian
The only people who can actually answer this question work for Apple, and they're not going to tell you.
I believe that MT is compiled to native code in such a way that it's not possible (within reason) to determine that it wasn't written in native obj-c in the first place.
And I haven't heard of any MT apps being rejected specifically for violating 3.1.3.
allow me to end this for all of you!!!
http://www.apple.com/pr/library/2010/09/09statement.html
As a MonoTouch developer with apps in the iTunes store (for example http://escoz.com/cracklytics), I can tell you that Apple is currently accepting MonoTouch apps normally. They approved 2 recent updates I did to the app with no issues.
Regarding new apps, lots of people in the #monotouch irc channel also have their new apps approved every other day, with no issues. Nothing changed because of 3.1.3 so far.
I wrote more about it here: http://escoz.com/monotouch-is-alive/ . Neither Apple or Novell have really mentioned anything regarding an agreement, so nobody really knows if they now have one or not.
Apple amended 3.1.3 to allow you to ask for an exception for your application. That might be what is going on, or architecturally it may not matter to Apple.