I have published an app on Google playstore but later realized that I needed to have the package name in lower case, so the name is still the same, only lowercased. But it seems the console picks it as different, meaning it is case sensitive. is there any way I can rectify this without having to publish it as a new app?
Related
In Xray test management and within a Jira environment, the requirement status of the story is not changing to (not Run) when I linked it within a test from the test importer (using a CSV).
Is it a bug? If I do the same manually, the requirement status is changing.
Does anyone have a solution for this?
CSV like:
Map of coverage:
I tried to replicate this issue in Xray cloud and it works fine; since it's a SaaS solution, it should behave similar on your end. At first sight all seems to be ok. Nevertheless I'll share some instructions that may be helpful.
Things to check in order for the coverage in a story to show as "NOTRUN", whenever we "add" a Test issue to it:
make sure the Story is configured as being a "coverable issue type" in the project settings
make sure you're adding the Test issue type from Xray and not another one which may have a similar name (somethimes this happens in some environments where people try other tools or create their own issue types by hand)
whenever creating Tests and linking them to requirements/user stories by using the Test Case Importer, make sure you map the CSV column where you identify the Story issue key to the 'Link "tests" outward'
if all the previous are ok and the problem persists, you may try to reindex the project; go to your project settings > Apps > Xray Settings > Reindex (info)
if the last doesn't work, please reach out to Xray support team so they can have a look it in more detail with you
We have been trying to set up the sample app for Play Billing workflow with subscriptions as we are looking to introduce subscriptions in our app. We wanted to have the ClassyTaxi app running end to end in order to understand the flows better. Although for past 2 days, we are only trying to debug issues and/or missteps because of some really poor documentation on Google's front.
After ensuring every single step was correctly followed, we were able to make some progress and have the app working with the correct Skus as configured in Play Console. But now the backend server (ClassyTaxiServer) is throwing below error:
"Unexpected error when querying Google Play Developer API. Please check if you use a correct service account" - "OtherError: The project id used to call the Google Play Developer API has not been linked in the Google Play Developer Console.".
We have relooked, recreated the service account on the Cloud Console several times, but no luck.
The Play Console is correctly linked with the Google Cloud project and the access is correctly granted to the service account.
Anyone has any suggestions? How can a sample app be so difficult to set up and function as expected? Or are we doing something terribly stupid?
Please help.
Thanks.
I passed trough similar situation, and I get same issue. After checking I found a note in google documentation saying the following:
Note: As of December 1, 2019, the Google Play Developer API is available only for version 3 and higher. If you're using a lower version of the API, you must migrate to version 3 by this date. For more information on migrating to version 3, see Changes to the Google Play Developer API.
Investigating the implemented code I found that the sample uses v2 of the google API (check ./subscriptions/play-billing/PlayBilling.ts line 70). So to avoid this situation, you will need to set it to v3, and update googleapis dependency to latest version in package.json.
Additional Notes
After solving this issue, I had a different message in 'OtherError', this time is “The current user has insufficient permissions to perform the requested operation.”. I will note my solution here just someone passed through similar situation:
In google play console, and after clicking on 'Grant access' in 'API Access' tab, you will need to select the user and add some permissions to the user (in my case I set it to admin, but I think it's larger than needed), make sure also to add the app/apps you are listening to.
If the issue is still running, just edit any of your products or just try creating new one, this step will clear the google cash and refresh permissions. (Check this question).
Background:
I'm quite new to App Maker, but have been involved in programming/IT for over 2 decades.
I have created an App Maker app, which works fine. It is deployed, and functions internally in our organization.
It accesses a Team Drive spreadsheet, makes modifications to it based on input criteria, and sends an email out to a hardcoded user. It uses no external GCP database or other resource.
The OAuth scopes it requires are:
admin.directory.user.readonly
drive.readonly
script.send_mail
spreadsheets
userinfo.email
Problem:
I can no longer preview the app.
When I click on "Preview" at the top right, a new tab opens and a spinning wheels seems to indicate that the preview is loading. Within about 4 seconds, the tab closes and the original tab (with the scripts, UI etc) gives a "Previewing failed. Dismiss" error in the bottom centre.
I am both able to deploy the exact same code/UI/etc, as well as run it without issue.
I do not know what I changed, since being able to preview the app, but cannot seem to regress to that state.
What I've tried:
Admittedly not much, as I don't know where to look. I'm rather certain that there must be some setting somewhere, but for all my googling, I've come up empty.
This can't be a client/server script or other syntax issue, as otherwise the deployment also wouldn't work.
With a more meaningful error, I would know where to look.
Expected Result:
Obviously, I should be able to preview the app if it is deployable.
Following #Morfinismo's comment, I contacted G Suite Support; my matter was escalated to the API Team.
I was asked by Google Cloud Support ("Support") to provide network traffic info using FiddlerCap. As I am on a linux machine and FiddlerCap is a windows application, I suggested alternatives (eg:Wireshark). It was eventually not required and never provided.
I noticed that on the Google scripts page, when accessing the project in question selecting "Preview", it was missing the following OAuth:
https://www.googleapis.com/auth/admin.directory.user.readonly
The functioning deployed version did not have this missing.
Still in the Preview, I selected "Stackdriver (logs)", which gave me an error that the project had been deleted. The actual wording was:
Access forbidden
Project XXXX is shut down and scheduled to be deleted. A project owner can cancel the shutdown on the projects list page.
Clicking on the link in the error "Go to projects list page" brought me to a page with the title "Resources pending deletion", which did not load a list of projects (but otherwise fully loaded) and would display the spinning wheel in perpetuity. I attempted this multiple times, including leaving it overnight once.
Support presumed that I had deleted the GCP project, although I honestly don't/didn't think I had. I also confirmed that creating new previews did not work, but creating new deployments did. I also confirm(ed) that this particular App Maker app did not require (eg) a GCP SQL database.
Support pointed me toward the following website: Google undelete project and I was asked to follow these steps (copy-pasted here):
a. For projectId, enter your project ID. From the screenshot you provided, this is "XXX (redacted)" (the quotes are just to emphasise the project ID, you shouldn't enter them.
b. Click EXECUTE.
c. You'll be prompted to grant authorisation, which may be preceded by a prompt to choose your admin account. Please do so.
d. You should receive a 200 response, with an empty body, that is {}.
e. Attempt to access the project via Project link (with the actual project id redacted here).
The above yielded some strange behaviour:
a. undeleteing the project gave it a different name that the App Maker app;
b. I notice that I had 3 other projects all called correctly (the App Maker app name).
c. When asked to reauthorize, I was provided with yet another project name ("Untitled project"), which was different from the correct one and different from the one in para. 7a, above.
d. I then also obtained another error in a new window which read:
That's an error
Request Details
(a bunch of stuff)
That's all we know.
Support advised that there may be a propagation issue, and that I should wait up to 30 minutes. I did, and it then worked! The only weird thing was the project name was wrong, but it was only for the preview, so I didn't really care.
If anyone needs additional information, I can PM screenshots I took along the way.
Hope this helps someone!
SJL
I have a Shiny app that I previously deployed to my now-defunct account on shinyapps.io. When I try to re-deploy using:
deployApp(appName="my_app")
I get the error message:
Error: Please specify the account you want to deploy
'my_app' to (you have previously deployed this application
to more than one account).
So I specify:
deployApp(account="new_account",appName="my_app")
But now I get the error:
Error in serverInfo(server) :
name must be a single element character vector
Based on this bug report, it sounds like I need to specify a server, but I am not sure where to find this information. For example, serverInfo() returns an error as well.
How can I get the relevant server info, or better yet, how can I deploy the app without all these workarounds?
Recently I have Added the my Android and iOS project to Firebase with alpha version.I want to See different Analytic and Crash for Staging and Production. Can anyone help on this.
Thanks
You have several options, depending upon what your needs are. The bottom line is that you should, at the very least, assign different application IDs to the different variants of your app, so they can be separate in the Firebase Console. You can have multiple apps per project (each assigned a different ID), or multiple projects with an app in each one, depending upon what works best for your team and your app.
The actual implementation can get complicated from here on out, so I suggest you read this blog post to learn about the options for your Android app, and how it affects the operation of the various Firebase features in that app.
I think of 2 ways to do so:
Using app version + date range: If you know your app in staging was version X from day N to N+10, you can select theses filter in Firebase analytics to display only the analytics coming from that configuration. This also work for crash reporting.
I prefer: Using a remote config & user property:
Setup in remote config a key as "environment" with some values like "alpha", "beta", "prod". You can then specify the value per platform/app version.
On the phone, read that value in remote config and track a user property in Firebase Analytics that reflect that value.
Finally in the Firebase console you can filter by user property (& app version if necessary).
With this option, when you move an app version out of alpha to beta (for instance) you just need to go in remote config, and change the value for that app version to "beta". This solution doesn't work for crash reporting.
You can use a different Firebase project for each stage so that the analytics are completely distinct. See more on that in the response to this question.
Create a user property Environment, give values such as Dev, Staging and Prod to it on build time.
Change the user property from client side to any of the above three mentioned values based on the build type.
Apply filter by Environment user property on firebase console to see the analytics data.