My company publishes multiple white label iOS apps from different developer accounts, and I'm in the process of implementing Sign in with Apple. On the developer portal I can see that it is possible to group multiple apps under the same developer account, however our scenario is slightly different as we use multiple developer accounts.
To clarify, all these apps connect to same platform, and users are expected to hold a single account that can be used across all of them.
Is there a way to use the same Sign in With Apple in both apps?
Just to update whoever may concern,
eventually the only solution was to move all application to the same developer account. we did the account immigration process and the sign in with apple works well on both applications.
Related
I have a use-case where I need to use apple login on two application (one has a iOS mobile app also) which belong to the same company but have different logos, is it possible to use the same apple login service in both. More specifically I had an issue with apple private relay with hide my email, as the accounts were duplicating on my iCloud profile. Is there way to link those two client_id so they don't create duplicates.
I've checked the apple documentation but it doesn't cover this topic.
I have created an app for my company. To use the application, you need to log in to the account that We ourselves create for each specific employee, registration of new accounts in the application is not available now and will not be available in the future, since only We can create new accounts for new employees and delete old accounts on our server .
Can such an application be published in the App Store, given the new requirements of Apple?
Is there any way to avoid this? Maybe if our application is unlisted, then it will be allowed to be published without explicitly registering new accounts?
We tried to submit our app for review and provided a demo account, but we were denied publishing due to implicit registration in the app.
As I know, you can create test account from your backend and provide this account authorisation info to the apple review team, so they can authorise and test your application
It is not the lack of user registration that is causing your app rejection.
For an App to be made available in the App Store it needs to be applicable to a broad audience. It sounds like your app is only for a very limited set of users; employees of your company.
For these types of apps you can use custom app distribution or unlisted app distribution.
Custom app distribution works well when an app needs to be made available to one or more organisations who manage their devices. (You can use it with unmanaged devices, but distribution is more complex).
In your case, it sounds like an unlisted app would be the best approach.
In both cases you still go through app review and will need to provide a demo login.
A third possible approach is to use an Enterprise developer program. Due to abuse in the past, Apple discourages these now that custom and unlisted app distribution is available. Enterprise programs are more expensive and are not granted to smaller companies.
Am developing applications for my customers I want to publish multiple apps for multi customer but I want to share all apps under my account with single certificate or customers accounts but i want to use single certificate for it, in future I need to update all apps with same time. I don't know how its possible. Please give some ideas. Apple store.
You have to used the cerificate for the app which is confugird in an Apple developer account.
You can create a single (dev. or production) certificate from an apple developer account. And using that ceritificate you can create provisioning profiles to distribute or debug the app.
As per my understading of your problem, You will have different client account for different apps. So you can not merge things into one. As apple developer account are separate to each other. you can not club into one. So the app publish from a account can be manage from that account only.
What you can do is if the client is signed up as an organisation then you can invite yourself as a developer into that apple developer account. In that way you can have the access to your client's account.
I work in a App Development company, we've developed and designed an app entirely from scratch, published with our own enterprise account, but Apple reject based on a strange rule:
"Guideline 4.2.6 - Design - Commercialized Templates and App Generation Services
Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences. Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or “picker” model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event."
We're not using any template on app and we are not a mass-app generation company. How can they say we've using templates?
Has anyone have similar problem and can help me with that?
Even though the rejection message is rather generic the main point is:
You can no longer publish apps for 3rd parties under your own developer account. (I assume that you meant organization developer account, because enterprise developer accounts cannot publish on the public App Store)
So as an agency or developer, you can still develop the app for your customer. But once it's ready, your customer will need his/her own developer account. They can invite you to the account and you can upload the app for them. Apple is also pushing organization developer accounts, so it's also no longer possible to publish company apps under individual accounts, even if you work for that company.
I have an Apple Developer iOS Membership. I have hired a developer to write an iOS app for me. They said they don't have their own account so in order for us to test the app using ad-hoc provisioning we'll need to use my account. When I go to invite users into my account from the Member Center I am given 2 options to add this user as, 1) Admin, 2) Member. Is the correct way to give a developer access and which option should I give them? I want to give the least amount of privileges as possible. I don't want them to access any sensitive account information, just allow them to develop the app and allow for testing.
This is the overview of the roles but I am still not sure which is correct
https://developer.apple.com/support/roles/
It depends on what level of involvement you want to have with the project. In order to manage the full development life-cycle for an app you need to create provisioning files, generate certificates for distribution, generate App IDs ect. You can add you developer as a member but in that case many of these functions will have to be done by you as the admin. In the case of certificates (for distribution, push notifications etc) the 'member' can request them but they still need to be approved by an 'admin'.
So, if you want to give the least amount of privileges stick with the 'member option with the understanding that you will need to be involved periodically.
I guess Member is what you should go for.