Goal:
Create many fake users for development testing.
What I did:
Added 4 test users with different names on Cloudkit Dashboard as bellow:
Result:
The 4 created users show up on app with same name (always the name of the last one created).
Question: Is it possible to create multiple test users on Cloudkit Dashboard?
The way I create test users for CloudKit apps is by adding Apple IDs I own as admins of my app in App Store Connect: https://appstoreconnect.apple.com/access/users
Then in the CloudKit Dashboard, I go to Container Permissions and give them access to the CloudKit container. I then sign them in on test devices using my app.
This might be more convoluted than you want, but if you don't manually manage users in your app, it might be the only way.
Related
I have a react/django project and we need to somehow access the contacts of our users. I was told to look into CloudKit's API in order to take care of this, however there seems to be no real information in their docs or in my Google searches on using this API to specifically access a user's contacts.
I am open to other suggestions as well. The ideal would be to access their contacts initially and then every so often compare their contacts to our list to see if any have been added.
You cannot access this data from a third-party app via a CloudKit API.
While Apple does store a user's contacts on CloudKit, they do so under these conditions:
The user opts-in to sync their contacts with iCloud (this isn't required for iOS users; they can be on-device only, or sync with another service like Google).
The contacts Apple stores on CloudKit are in a container that is private to Apple.
When you use CloudKit as a developer, you are creating a container for your app. You can only access data in containers you create.
Here's what you would have to do:
Create an iOS or macOS app that requests/manages access to the user's contacts.
Add the Contacts entitlement to your target in Xcode: Signing & Capabilities > App Sandbox > App Data > Contacts
Use Apple's Contacts framework to access contact data using Swift in your iOS/macOS app.
Once you have the data in your Swift app, communicate with your Django API to do what you need to.
One last thing. If you choose to go this route, you will have to reveal in your app privacy disclosures (in App Store Connect) what you are doing with the users' data.
I'm wondering if it's possible for me to access a user's private database on the Development schema as the app developer. I'm just testing locally on my devices, but I need to be able to inspect the records of devices not associated with my developer account for debugging purposes.
Thanks so much!
The only way to do this is to sign in to the CloudKit Dashboard with that user's Apple ID. Their data is otherwise private.
Alternatively, you could create a mechanism in your app that pushes a user's data to the Public database of your app for help/troubleshooting purposes. That data is visible to you there as the app developer and you could download and inspect it.
I do custom iOS development for small companies. These companies have me completely manage their apps. The problem is that these companies apps show up on my company's App Store Account. Example: There is a mix of apps on the "More from this Developer" line.
I would like a way to manage all the apps I create in one itunesconnect account but have the apps deployed in such a way that they do not appear to be related and the "Developer" appears to be my client instead of me.
Is there a way to do that?
The purpose is to hold down the pain of switching accounts to manage the release cycle of the apps.
Each company will need to setup their own developer account (as an organization account) over at https://developer.apple.com/programs/enroll/
After that, they can invite you/your Apple ID as an admin and you can switch teams on App Store Connect / Apple Developer Center. With admin rights you have full access to setup everything for those customers and they also retain all IP, analytics data etc.
My question is about Facebook Ads API's March 4 breaking changes regarding the new campaign structure.
I do not have a test account nor a test app yet. I would like to test whether my code supports all the March 4 breaking changes. I have neither a test account nor a test app. I have requested a test account through email (this was suggested in the change FAQ). I will later whitelist the account for accessing the structure changes.
To get the test app, do I have to use only the test account (creating an app requires a developer account) or can I create the test app directly by using my production facebook ads account?
Also, the page to apply for test ads app is the same as getting a normal ads app. FAQ suggests that I add "test" to my name. Is this all I have to do or is there something more? The link for helping set up app in the FAQ doesn't seem to point to the right place and doesn't help.
1-To get a test app all u need is to be a developer. Once the app is created u can use it with a test/production account.
2-test and production apps can be created from the same place. Just put "test" in the app name.
We built an iOS app and released it on App Store with a Facebook App Id, which was created by one of our developers using his own Facebook user.
Now, the developer has left and we need to alter a few settings of the app, but we do not have his login credentials to login as him. I know it should not have been this way to start with.
We do have the Facebook App Id, in the code.
What are possible solutions to this:
Is it possible to transfer the app to another user?
If I create a new app with another user and use the new Facebook App Id, how would it affect existing users of my app?
If you create a new app it will have an entirely different app id and secret. Your users would have to sign up for the new app. You would not be able to migrate the users to your new app, they would have to authorise it as if starting from scratch.
What you need is to get the old developer to add one of your accounts as an admin role to the existing app. This would give you complete control over it. Obviously this involves getting in touch with your previous developer and hoping they are nice enough to do it!
There is a section called "roles" on the dashboard for an app. This is where they will need to add your account.