I'm trying to publish a closed test on Play Console, however, I get this error "Unknown validation VALIDATE_APP_MESSAGE_ILLEGAL_TO_DISTRIBUTE_IN_SELECTED_COUNTRIES". Even if I select one country, I get the same error.
This looks like a bug.
The error message should normally tell you that you are not allowed to publish in this country based on your content rating.
Related
We converted country/states in Salesforce to the standard picklist. Heroku doesn't seem to reflect those changes as we get loads of errors in Heroku like the one below when Heroku syncs with SF. I re-polled the account object in Heroku to refresh the account table but still the same errors. The country/state picklists are considered meta data in Salesforce in case that helps to understand the issue. Does anyone know what needs to be done in Heroku in order to get the updated list of countries/states that is now in Salesforce?
"AccountsTrigger: execution of AfterUpdate caused by:
System.DmlException: Update failed. First exception on row 2 with id
0033X00003solkfQAA; first error: FIELD_INTEGRITY_EXCEPTION, There's a
problem with this state, even though it may appear correct. Please
select a state from the list of valid states.: Mailing State/Province:
[MailingState] Class.AccountHandler.HandleAfter: line 154, column 1
Trigger.AccountsTrigger: line 17, column 1"
You might have more luck on dedicated salesforce.stackexchange.com site. It's hard to say, sounds like error thrown from a trigger handler but you didn't post any code. Would be also good to know what do you have, the Heroku Connect product or some custom integration that happens to be deployed on Heroku?
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/compound_fields_address.htm what are you mapping in your integration. Account.BillingCountry or Account.BillingCountryCode?
Worst case you could try contacting support
I'm trying to set the changelog via Fastlane:
changelog = changelog_from_git_commits(
commits_count: 1)
upload_to_testflight(changelog: changelog)
This causes the following error:
Could not set changeling: {"code"=>"ITC.apps.tf.build.missing.primary.test.info", "description"=>"Missing primary test info."}
This is an app used for internal testing only. I didn't fill in any information on "Test Information" because I don't want to accidentally release it to external testers.
I tried unchecking the following box:
It still shows the same error message.
What's the minimum amount of information I need to get this to work?
I'm on fastlane 2.108.0. I found some related information here, but that's mainly with ITC.apps.tf.build.test.info.missing.whats.new, which is not the exact error I'm seeing.
Navigate to:
App Store Connect
Choose your App
TestFlight
Test Information
You will probably see this error message up top:
⚠️ Complete test information is required to submit a build for external testing.
You can ignore that. For an internal test to work, you don't need any information on here. However, to get Fastlane's changelog feature working, you'll need to fill in the following details...
primary.test.info
Could not set changeling: {"code"=>"ITC.apps.tf.build.missing.primary.test.info", "description"=>"Missing primary test info."}
You're missing a "beta app description":
test.info.missing.feedback
Could not set changelog: {"code"=>"ITC.apps.tf.build.test.info.missing.feedback", "description"=>"Missing feedback email."}
You're missing the "feedback email":
So as a minimum, you need to fill in the following information when using fastlane's TestFlight changelog feature:
Beta App Description
Feedback Email
When generating a Search Report for any collection, the report status appears as "Complete". However, when i attempt to View or Export the report i am getting an error indicating "Internal error on generating report.".
I am able to 'Update' the report to regenerate the report however, the same issue occurs when i view/edit the new report.
Event logs don't show anything other than the report generation event.
I'm pretty sure that's a known bug that's fixed in one of the most recently released patches. Log a ticket with Google and they'll give you the details and should be able to give you a support script that you can run for a temporary fix until you apply the patch.
I am getting an error when attempting to create a new project for Google API at https://code.google.com/apis/console
I was hoping the error was temporary, but I have been unable to create a new project for a couple weeks now.
The error seems to have changed, as it used to include server ip information and a lot of other data. An example with some potentially private information removed:
APPLICATION_ERROR;google.cloudresourcemanager.projects.v1beta1/DeveloperProjects.CreateProject;com.google.apps.framework.request.StatusException:
generic::FAILED_PRECONDITION:
;AppErrorCode=9;StartTimeMs=1489595147198;tcp;Deadline(sec)=50.0;ResFormat=UNCOMPRESSED;ServerTimeSec=0.027545452117919922;LogBytes=256;FailFast;EffSecLevel=none;ReqFormat=UNCOMPRESSED;ReqID=removed;GlobalID=removed;Server=ip:port
Now the error is a lot shorter, although still seems to be related to the same cause:
com.google.apps.framework.request.StatusException: generic::FAILED_PRECONDITION:
The spinner in the dashboard appears to spin forever, while the error appears underneath alerts after a few seconds. I have tried numerous project names and all fail with the same error.
Is there some type of quota I am missing that is preventing this? The quota menu item requires me to select a project, which I don't have any.
Clicking on the error brings me to a page with the following message:
You don't have permissions to perform the action on the selected resource.
Make sure that the Google Developers Console is on for the user that is trying to create the project.
Admin.google.com > Apps > Additional Google services > Google Developers Console and turn on for any org or user that needs it.
Looks like there's another possible cause, in addition to the one that #AndrewL provided in his solution.
Short answer:
I ran into the same error when I attempted to associate a new GCP project with our billing account via Terraform. Our billing account has a default limit of 5 projects (which we had already met), and this blocked the association of new accounts and generated the Error 400: Precondition check failed., failedPreconditionerror message. To fix, I had to remove/delete one of the already associated projects before I could add a new one.
Long answser:
Here is the error message I encountered in Terraform (sensitive data and IDs redacted):
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ module.<MY MODULE PATH>.project
billing_account: "" => "<MY BILLING ACCOUNT ID>"
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
module.<MY MODULE PATH>.project: Modifying... (ID: <MY PROJECT ID>)
billing_account: "" => "<MY BILLING ACCOUNT ID>"
Error: Error applying plan:
1 error(s) occurred:
* module.<MY MODULE PATH>.project: 1 error(s) occurred:
* google_project.project: Error setting billing account "<MY BILLING ACCOUNT ID>" for project "projects/<MY PROJECT ID>": googleapi: Error 400: Precondition check failed., failedPrecondition
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
My billing account was at its maximum of 5 projects. As a test, I removed one of the projects and then ran Terraform again. It then successfully added the new project to the billing account. To double check, I attempted to add yet another new project to the billing account (to push the amount to 6) and then received the same error message again.
Straight up deleting one of the associated projects also works.
It stands to reason that requesting a limit increase for your billing account's associated projects will also fix this issue.
Another possible reason for this error can be accessing the .xlsx file. If you are accessing this file using Google spreadsheet then you need to save the .xlsx file in to save as google sheets by choosing the option available in the File menu at the top.
Thanks
Another possible reason for this is Organization policy, denying the particular API on ORG/Folder/project level.
For me the error was working because I was trying to read the file from a shared google folder. Check if the drive where the file lives is your drive and not a shared one.
I want to assign alerts for my team project as followed:
1. Every build that failed will trigger an email notification for the last developer that committed a change.
In additional send the same email to the code reviewer.
I only found that a failed build will sent to all team members an email or to me and I cant change the "Sent To" field (its disabled and I'm administrator user)
Another issue I encountered is that when a build failed the email I get states that there is 0 errors and 0 warnings. How Come?
It's supposed to be fairly easy to configure but didnt managed to get the email right.
Can someone assist here?
This is the email I get, a failed build with 0 errors, when entering the build url I can see the where the build has failed but how can I know it from the email???
You can't change the "sent to" filed, however you can choose the name of the team member from the drop down list, or type the name in the search box.
Choose the name of the team member from the drop down list, or type
the name in the search box.
For the people who trigger the build (which one need to be reviewed), he can specify the coder reviewer and add a build fail alert, add the filter request by = [Me]
As for question 2, there is 0 errors and 0 warnings.Which build are you using? vNext or xaml? And did you mean the build actually failed with errors but it's not reflected in the email.
Update
The errors and error message should be contained in the e-mail just as below picture.