I have a dev, stage and production app in a Quickblox account. When testing I'm signing up a new user in production. There are no users in my production app and one user in my staging app.
I'm getting an error saying the external id has already been taken. Looking in the logs I'm definitely connecting to the different apps.
Is this the correct behaviour? Do I have to create a new account if I'm going to be using external ids with multiple apps?
Yes, this is the correct behaviour. User base are shared between all apps, so you can have a line of apps and all users will be able to use the same login+pass to sign in.
To avoid such things you cab create another Admin panel account and use it for dev/qa envs.
Related
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.
How could I easily change the match configuration so it continues working with a new user?
We had a person who was account owner whose account was used to perform the build via FastLane. Since Apple introduced the new 2-factor authentication which is mandatory for the account owners we had to either authorize computer via 2fa occasionally or use some other account which is not of account owner role. We want to change the user to the specialized account only for fastlane builds. I have a feeling I will need to nuke everything and start from scratch but I would rather get some input before doing that.
I already created accounts needed for apple developer portal and for iTunesconnect. I changed fastfile, matchfile, deliverfile and .env but it always pulls the old user somehow.
We are using the git for storing credentials but as far as I know I should not have to touch anything there since it's only used for sync.
I tried using
fastlane match development
And it verifies on the portal but then it installs old users certificate.
I have an app on store and all client are used it. Sometimes some client needs additional feature that isn't wanted by others so in that case I make AdHoc build for that particular client, but it is not proper solution.
I think on Enterprise solution but apple not allowed to distribute outside the organization in it and I have all users are clients.
If your app has a user login, download a user specific configfile directly after login and check in code for feature availability by looking into it. Large companies like Spotify and also startups do it this way to test new features without releasing them to all.
I'm pretty newbie in iOS development but I'm trying to figure out how to organize the authentication. I need the authentication because of 2 reasons:
In-app purchases
User can add his or her own data into common database.
I supposed that as soon as user downloaded my app he or she will be easier to use the Apple id to authenticate but I have no idea if it's possible to use Apple id in this situation and how to organize this authentication on my server.
For information: I'm going to use Node.js as a backend with MongoDB, hosted on Windows Azure portal.
The workflow is:
User downloads and runs my app
User uses it (without any authentication so far)
If user wants to add his new data and share it the data should be
sent to the server and user must enter some credentials.
User enters Apple id credentials (and user name under he wants to
share data?) and sends his data to the server.
Further if he wants to do app-in purchase he uses the same
credentials.
If it's even possible? If I can't use Apple credentials to send data to my server, if it's possible to use other credentials (my email, or OAuth) to make app-in purchase? I don't like to idea to make user enter different credentials twice.
Thanks!
I need to add log in screen and registration forum to my application, such that the user register or log in to the application,
is it legal issue or my application will be rejected
You can have a log in screen. Many apps have them.
But Apple has been rejecting apps with a login registration screen, or even a registration web site URL within the app, depending on the exact conditions for that registration. You may have to get users to register for your app outside your app and/or before running your app. Make sure to preregister Apple with a demo account for use during app review.
It also helps greatly if your app has some general usefulness even without registering (e.g. banking apps may have a map to the nearest branch even for users who don't have customer account logins, or some public info about interest rates, etc.).
There are plenty of apps that also live on the web and so require some sort of login, e.g. Foursquare, Facebook
There are no issues at all with creating a login screen for your application. When you submit your app to the App Store, you will be asked to provide login credentials for the testing team to login and test your app. I wouldn't force them to go through the account creation process as it may delay your app getting approved.