When I use test flight for my app, and I want to test my Game Center capabilities, will I have to make sandbox accounts for all of my test users and instruct them on how to use those accounts, or can they use their normal accounts?
They can use their normal accounts, but they have to have sandbox mode turned on under Game Center in their settings. This will create a new sandbox account for them using their normal account.
Apples developer guide says:
Important: If your app uses Game Center, testers will be required to turn on the Game Center sandbox from their device settings in order to use the Game Center features while testing the app.
Related
Is there a way to specify one list of apps to associate with all the test users in a group created using the meta quest developer console, such that when each test user account logs into a given device, all the specified apps appear in the library and can then be installed from the app menu without searching for each app? These would all be freely available apps in the meta quest store, not in-house developed apps for testing.
Hi I am new to IOS automation and I have a scenario where we have to do an In-App purchase
As for Testing these could be done by AppStore Connect Portal under User Access and create a Sandbox account but is there a way by which we can create an Apple (Appstore Connect) Sandbox account programmatically
Please advise
Well, it isn't much of a solution and it is a PITA but you could use something like Appium, which is what I use, to automate all that stuff by driving a web browser.
I use it for testing 3rd party social logins. For things like Apple ID where the social login requires 2FA I have an Appium test step that goes to a google voice account in the mobile browser and retrieves the 2FA code that was texted to the GV number. It is tedious and a bit brittle but I couldn't find any other way to get around 2FA situations.
Is it possible to install a Dialogflow chatbot for testing on my Google Home device
without using the phrase "Talk to my test app?"
I am a rather new user of Dialogflow and have several simple test apps that
I plan to develop as learning exercises. Can set them up for testing on my
personal Google Home device without entering the "Talk to my test app" and without
submitting them for distribution to the Google Home community. I do not consider them
sinificant enough to offer them the the Google community at large.
I anticipate the develop of the following apps: 1 - SillyNameMaker, 2 - Woodchuck,
Gettysburg Address.
Thanks for any help
Jim
If you provide an app name and sample invocations in the "App information" section of the Actions on Google console, you'll be able to use this name to invoke your app on devices that are signed in to the Google account you are using for development.
One thing to note, however, is that you can only have one app in testing at a time. If you start testing a new app, the previous one (even if it is named) will be unavailable.
I am trying to use a Sandbox Tester Account on my Mac to test In-App purchases with the Mac App Store. From Apple's documentation it seems I need to sign into my Sandbox Tester account on my Mac to test this functionality.
I have a few developer accounts, in addition to a sandbox tester account, in Xcode. How can I determine (and change) which account Xcode uses when my app queries Apple with the SKProductsRequest API?
I am running the app directly from Xcode.
As #LeoNatan pointed out, just sign into the Mac Developer account with the Sandbox Tester account. This will be enough -- the app will then use that account for communication via SKProductsRequest
I'm trying to implement in-app payment support in a BB application.
Ok, I've read the API/docs and now I need to write a simple test. Here is what API says about testing:
To test the end-to-end purchase flow without being charged money, you can set up a BlackBerry ID as a test account. The test account allows you to download any applications or digital goods that are associated with your BlackBerry App World vendor account without incurring any costs. Local testing must be turned off for this type of testing, otherwise no network connections will be attempted.
From the above I see that I need to achieve 2 goals:
(1) "set up a BlackBerry ID as a test account" (what ever it means).
(2) "Local testing must be turned off for this type of testing" (what ever it means).
The API is vague on how to do that. I can only guess that point (1) can be done on the side of my customer (whom I'm writing the app for) via his AppWorld account. Is it true? And I'm totally out of ideas on point (2). Could anyone point me in the right direction?
Ah yes, the Payment API is particularly vague on testing, and in the latest version (1.5) RIM have removed the ability to test locally, so all testing must be done via App World. Here's how:
Setup a 'sandbox' account using the BlackBerry App World vendor portal
Upload your app into BlackBerry App world but don't publish it, just save it and leave it in draft state
Also in the vendor portal, set up your digital goods (the things available for in-app purchase)
On your BlackBerry, load App World and login with your sandbox account email address.
Within any screen in App World press ALT+TST and enter the SKU or ID of your test app.
You can then download the test version of your app (which is not available to anyone else)
Once the app is downloaded and installed you will be able to test your in app payments.
Bit of a faff, but not too hard once you've got the process sorted.