| Would it not be simpler to either use the custom B2B developer option, or have your client purchase an in-house enterprise app development license (as the web site states, enterprises can hire others to develop an app as long as everyone agrees on the ownership certificates). The custom B2B app sounds like it might fill your bill (you go through pretty much the same development and review process; when you go through the submittal process, you set up certain switches to limit to specified Volume purchases, your client gets a Volume purchase agreement with Apple, and, depending on your whims when you submit the app, they are the only company that can download the application). I think you may run into problems with your approach. When you withdraw the program from the App Store, existing downloads may work, but, new downloads won't be possible, and you won't be able to put existing copies on new phones for new owners because certificates won't jibe.
On Sep 23, 2012, at 4:39 PM, IPhone Lover wrote: Thanks Jim,I have submitted 4 to 5 apps to App Store without any problem. But this is the first enterprise app which i am going to submit to the app store for review(and i know we do not actually need to get the review, but my client is insane) and trying to pretend that we will put on app store.
And i am 100% sure, that apple will reject the app, if we are asking to the user for login credential to get into the depth of the app. On Mon, Sep 24, 2012 at 2:02 AM, Jim Geist <email@hidden> wrote:
It's your app, and your (and your client's) risk to evaluate. I'm just pointing out something that you might want to consider, not trying to tell you what to do.
On Sep 23, 2012, at 1:29 PM, IPhone Lover wrote:
On Mon, Sep 24, 2012 at 1:53 AM, Jim Geist <email@hidden> wrote:
The point of review in Apple's process is to ensure the app is appropriate for publication on the app store. Yeah, that is why we are just pretending that we are going to publish it on app store. and we are providing them the login credential to get into the app.
Once they approve it, the only thing that stands between it and the app store is you or anyone else with access to the account not making any mistakes and accidentally releasing it in ITC.
Yeah and once they approve, we will reject the binary from our end.
I'm not saying it *will* happen, I'm saying from the perspective of security defense in depth, it's a potential risk.
Well, our data is not that much confidential. it just for internal employee.
On Sep 23, 2012, at 1:19 PM, IPhone Lover wrote:
How? We are putting up for review to just get the approval from Apple that we are making the best app. and i don't think Apple will reveal any confidential data to others.
On Mon, Sep 24, 2012 at 1:44 AM, Jim Geist <email@hidden> wrote:
It's worse than pointless. If the app is an enterprise app which is a portal to confidential data, then putting it up for review opens the possibility that it will become available to the general public, which is a non-trivial security risk.
On Sep 23, 2012, at 1:05 PM, Seth Willits wrote:
> On Sep 23, 2012, at 12:27 PM, IPhone Lover wrote:
>> • Will apple will accept such kind of app for review which is not useful for public …
> If the application is not useful the public, it will be rejected. It is absolutely pointless to submit it for review.
>
> --Seth Willits
>
>
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list ( email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|