Is it possible to migrate an app from a business manager to another?
We develop an app that required business verification and we associate it with a sandbox business manager, instead of the real one.
Now we want to correct this error and associate the app with to real business manager, but there is an error because the app is owned by another business manager.
I saw that in the wrong business manager it is possibile to remove an app, but what will happens? Will the app stop to work? What's the right migration procedure to avoid service interruption?
Related
I commissioned a dev on upwork to build my app for me and release it into play store and app store, the agreenent was that I own the code but the dev has been using his own signing keys,etc.
Do I need to create my own signing keys to put into the code? Or do I need to be doing this myself?
Should I create my own Play account? Can I get my dev to release it into my play account?
What else do I need to replace to make it mine so I dont have to rely on that dev to make changes down the road?
Anything else I should worry about?
In order to be owner of your own code and be completely independent for future releases with another developer you would need the following:
Your own account on the App Store / Play Store, so you can manage developer's access when they do the release of the app, but you keep the account and full admin access and they can't temper with the app itself once released.
Git (github, gitlab, bitbucket or any 3rd party provider) account and repository to which you give access for the developer, so he can commit code of the app. This preserves the history of his work + you can manage multiple people having access on the same codebase. Also already pushed code can't be lost on his local PC.
Other than that all accounts that are needed for 3rd party services also need to be created by your own account. An example would be Firebase console account or google account to access it's API for geolocation or any other 3rd party...
Regarding keys...all keys that are generated during the development time serve for that development period, and they can be changed later on when new developer comes onboard. The developer can share them with you, so you too have access to it all, but that's not something that can block your action on the account/application at any point when you break up the contract for any reason.
You should own your apple and google store account and signing key for every app released on the stores.
Of course you have to own the code but if you want to publish your app the code needs to be built and get signing and be uploaded on the stores.
You could make your developer in charge in building, uploading and getting feedback from apple or goolge store team or customers
The signing key do nothing changes in your code. it will be used only when build your app and devlier to the stores and somewhere else.
I want to share In-App purchased product identifiers from one app(say "App1") to another app(say "App2"). Both run on iOS 7 devices. And more importantly since "App2" was released long time back, both the apps have different Team IDs. When the user clicks on a "Restore purchase from App1" button I want "App2" to unlock certain features based on the purchases the user has made in "App1". What is the best way to achieve this?
I dont want to use UIDocumentInteractionController or UIActivityViewController because that would require unnecessary user interaction.
Key chain items or iCloud key-value storage cannot be shared because both the apps have different Team IDs.
Can't use an exclusive server through which the two apps can communicate.
You cannot do this by using the IAP API. You could store the information on your server and unlock it for a user, however, this is against the App Store Review Guidelines:
Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be rejected.
And technically you would not be using the API if you checked against your own server and provided the content through that.
Now this looks possible for subscriptions with App Bundles: https://developer.apple.com/documentation/storekit/in-app_purchase/offering_a_subscription_across_multiple_apps
You can offer customers auto-renewable subscription services that are accessible through multiple apps across one or more operating systems.
In order to offer this functionality, your server must grant access to the subscription content across all apps, despite the user having purchased the subscription within a specific app. You can use a unified account management database along with server-side receipt validation to validate a user's purchase and ensure in-app transactions are handled. By entitling subscription access from your server, you can provide users the ability to access your subscription across multiple apps.
It's Possible using Authentication API
step 1: When purchased product successfully to store status inside API
step 2: Then call API every time of didFinishLaunching to check purchase status and use multiple APP
Another benefit is make payment without any payment gateway...
I know that an account for full access of all features is required when submit an app for review.
Users of my app are in fact university teachers and students. Actually this app is just a third party one which I developed for iPhone users, for the reason that the original and official website of my university runs pretty bad and sometimes even fails on Safari. Obviously I don't have the access to the database to create a test account.
In addition, the auth server is only open for users inside my university (the IP address of the server is a virtual one for local network.) Even though I provide them with my own account, they will still not be able to login.
You can't. Apple will not review a login-required app if they can't log in to it.
Build a test server that interacts with the app exactly the same as the real client server except for being visible outside your clients secure network (and containing only a dummy data set, no actual private or proprietary data), create test accounts on that, test your app against that, then submit the app to Apple with a working test account on the test server.
I wonder if someone could offer insight here:
I work for an independent multimedia firm who builds communications material for their clients. We're currently working through our first iPhone app. So, my shop has now completed an app that conforms to our client's brand, and we wish to deploy this app to the App Store on behalf of our client. Looking over Apple's documentation, everything seems to be written on the assumption that you are releasing your own app... therefore, the Apple documentation seems to start one step ahead of where I need it to.
So, as a multimedia production firm, I have set up a developer account for my company that I have been using to develop our client's app. However, I assume my account cannot release my client's application, given that it would cite my company's name as the publisher. Therefore, how do I start this process on behalf of my client? Will they first need their own $99 developer account to publish with, or is there a separate publisher identity that I can set up within my account that represents my client?
Any and all help on this would be appreciated. Thanks!
I typically have the client create their own account. From there most clients will provide me access to their admin account so I can go through the rest of the steps.
I often submit apps through their admin account, however, a team member is an option if the client is not interested to provide admin credentials.
Does anyone have any idea of a service provider that provides In App Purchase with subscription model. I checked Urban Airship which has solution built around non-consumable approach and iLime is not available yet. Any pointers in the right direction would be appreciated.
Though i am not aware of the service providers, i will be able to tell you about tracking of subscriptions.
Tracking usually needs the user's connected 5 devices to be enabled with the subscription. For this, you either have to maintain another set of user credentials on the server and ask the user to enter the credentials once the app is loaded onto each device.
another approach is the unique userid for the device once the app is loaded. Upon installation on the second device, the same userid needs to be entered for enabling subscriptions.
Try to look out for newer version of ApalyaTv for more details.