I've generated promotion codes for my app in the play store and they work fine. My question, is there a way to know which of the generated codes were used to install an app?
Related
I'm using Google Play Store to distribute an app.
For a certain issue, I would like to install an OLDER version of my app to one of the client's device.
I'm struggling to do so, is there any way to do that?
No matter how and which "testing" method I apply, Google Play automatically shows the HIGHEST version of the app which is the "release" version ignoring the old test versions.
Creating an APK would be NO way because I need Google Play's own signature in the apk to make things work (to test the things we would like to)
Is there any way at all to distribute my OLDER app version from Google Play store?
(By the way Google's testing methods are inexpressibly unusable even apart from this problem. You never see what really happens, you cannot really manage the testing channels the GUI is miserable the notification email is late the testing is slow and painful you don't see the version number in the Google Play Store, there are like 3 methods to do so and the difference between them is not self explaining, I give 1 start to the developers who made these parts of Google Play I hope they read this.)
Thanks in advance.
From Google Play Console go to App bundle explorer
Then choose the version you want to install
Go to Downloads tab
click on Copy sharable link
install it from you device using this link
Note: the device's Google Play account should be an internal tester and enable internal testing from Google Play on this device.
We're trying to automate the release of our app to the Mac App Store. I've been trying to achieve this using fastlane. I managed to get this tool working for submitting the apps' metadata (release notes, screenshots etc).
I can also build the app using the gym module, however this results in a .app and not in a .pkg that is needed for submission to the App Store. Even when I use
export_method: "package"
I cannot imagine I'm the only one trying to achieve this, but I cannot find an answer if it is possible at all. And if possible, how to achieve this.
I have a (old) work in progress PR made for this - https://github.com/fastlane/fastlane/pull/12195. Majority of our users are mobile so it has been hard for me to get testing on this :). If you'd like to comment on that PR I would be happy to revive it and work with you on making this work for you!
My app to test depends on Facebook. On such devices which does not have Facebook installed, I needs to install Facebook first.
The first way I have tried is to install it from an APK file. However, I cannot find any APIs to achieve this from uiautomator developer docs. I guess this is determined by the design of uiautomator.
The second way I have tried is to install it from Google Play store. However, on the devices which has no Google account signed in, I need to sign in Google account first. I tried to sign in using uiautomator but unfortunately the sign-in page is NAF (not accessibility friendly).
Does anyone know if there is any other ways? Thanks in advance.
AndroidViewClient/culebra is a pure python tool that automates or simplifies test script creation. The scripts use UiAutomator as a backend.
Culebra GUI can generate tests that include the installation of an APK as a precondition.
culebra --install-apk=file.apk --unit-test-class --gui
EDIT
culebra only generates python, so if you want to generate Java or Kotlin you may need CulebraTester.
However, due to the limited connectivity and capabilities when you run those tests in Firebase Test Lab it might be challenging to find a way of installing dependencies.
Due to a well known and quite often discussed "keystore-signing-problem" I need to rebuild my app from scratch again in Google Play Store.
However I wonder: In case the "old" app will be disabled - can I use the same name for the "new" app again?
The two important things you need to pay attention to are the signing hash and the package name. You can only have a single app published per combination of SHA1 hash/package name. All other fields (title, app name, etc) and configuration within your Android app can be set to whatever you want and you should have no trouble with conflicts.
Now I have an around 30M app, when I need to make an update for the app ,I want to update only a little part of the app,what shall I do with the app? Should I make a updating app for the app or should I make it like downloading the whole new app every time?
I forgot to say that it is an app running on the Mac OS, not iOS.
Without more context, the best answer is "It depends". Off the top of my head, I can think of these factors which would affect your decision:
How many users use this app? What is
the bandwidth availability of these
users?
Do you expect the users to download and install the app? Or do they need
an automatic update? Has anybody
asked for an automatic update?
Is it a desktop app or is it a client server kind of situation?
Have you already split up the app into components so that you can ship
just a small component, replace it in
the deployed app and expect the whole
thing to work?
Edit: Based on context in the comments: Since the app is a playing music from some online source, I'm assuming it'll need to connect to some central server to play the music. You could make a small wrapper application around the music app. You'll need to change the installer such that the wrapper app's icon appears on the desktop and any launchers you have. So the user will launch the wrapper app first instead of your music player app. The wrapper app can then contact the central server and ask for the latest version of the music app. If the installed version of the music app is older, then the wrapper app can either automatically download the latest version of the music app or prompt the user to download it or .... Once the download and install finishes the wrapper should launch the music app as well. Depending on your situation, you can get fancy and make the wrapper app download only the changed portion of the music app, etc.