Hello everyone i have beenn working in several projects and all push notification were working either on developemnt or prodcution. However i am not getting this error : "Error in registration. Error: Error Domain=NSCocoaErrorDomain Code=3000" since yesterday. I have tried to create a new provisioning but its shut down for maintenance. Is it due to this?
Thanks in advance.
Ensure the Bundle Identifier matches the one in your project's
plist.
Create a new App ID, and configure it for production/development
push before creating a new provisioning profile.
Make sure you're build and archiving on the right target, with the
right configuration. You might need to go back to project settings
and double check with the correct configuration selected (I use
release for this).
Related
I have completed all the procedures in the development process of the Google Smart Home action including Invocation, Actions, and Account linking.
However when I try to test the same, If I go to test suit and log in with my developer mail id and paste my action's project id, It throws an error:
Error getting Home Graph: sync error: 403: Please make sure you have resourcemanager.projects.get permission on project 'project-id'
My bad, it was a more sort of invisible typo error.
I am not sure why, but when we copy the project ID from google action's console there is a space prefixed with the project id. Which causes this issue.
Make sure to remove extra whitespaces on both sides of the project ID and try again in the test suit.
Both my model and skill.json are up to date when I check ask diff, I made some changes to the lambda function in index.js, and when I tried to ask deploy, I got this error message:
[Error]: Failed to resolve the Lambda deploy state for arn:aws:lambda:xxx. Please make sure this Lambda resource is correctly mapped to the existing alexaUsage in the config file.
My understanding is that the config file is populated automatically and I didn't make any change to it... I'd appreciate it a lot if someone can help me understand this error.
Check if you have more than one profile configured in .ask/cli_config.
You can also back-up this file and create an empty cli_config file then execute ask init in the corresponding folder project to reconfigure the access token for the right account.
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
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.
When I try upload my app to app store I get the following error: "Unable to lookup the settings for submission for the application at this time due to a general error". Have anyone ever get this message? Is it due to an Apple developer portal problem?
IDEDistribution.critical.log:
2017-01-06 15:32:14 +0000 The store submission configuration response failed with errors: (
"Error Domain=ITunesConnectionOperationErrorDomain Code=1614 \"Unable to lookup the settings for submission for the application at this time due to a general error\" UserInfo={NSLocalizedRecoverySuggestion=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedDescription=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedFailureReason=iTunes Store operation failed.}"
), warnings: (
), info messages: (
).
2017-01-06 15:32:16 +0000 [MT] Presenting: Error Domain=ITunesConnectionOperationErrorDomain Code=1614 "Unable to lookup the settings for submission for the application at this time due to a general error" UserInfo={NSLocalizedRecoverySuggestion=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedDescription=Unable to lookup the settings for submission for the application at this time due to a general error, NSLocalizedFailureReason=iTunes Store operation failed.}
I have found the solution, before uploading the app by xcode, you should create the app at http://itunesconnect.apple.com/
I had the same issue, and after playing around I realized that when updating a new version of an app, the "Bundle ID" must match the original version "Bundle ID".
Matching the Bundle ID to my version 1.0 upload solved the problem.
I got the same problem, and I realized I made spelling mistake of bundle Id...
I'm getting the same for the last couple of hours.
From the verbose.log:
Bundle ID based store submission configuration response received = (null)
Looks like a problem at their end.
I had this same problem and I went to analyze my account on Itunes, I realized that I was as a Developer. To create apps and send versions to iTunes you must also have access to the Application Manager function
In Itune connect，App info： group ID + suffix ID must be as same as your Bundle ID in Xcode Info.plist
In my case the problem was that I had specified the wrong bundle ID in my app settings in xCode. It didn't match the bundle ID I had specified in iTunes connect.
Basically this setting in xCode:
Needs to match this setting in iTunes Connect: