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
Related
I cannot sign in with Sandbox tester ID (the fields are not even displayed in Settings-App Store).
I am running Xcode 14.2 and attempting to test on a developer-signed physical device (iOS 16.1.2). Following the steps in Apple documentation ("Setting up StoreKit Testing in Xcode"), I have been able to run tests using using local StoreKit configuration file. All works well. I next wanted to try to use Sandbox Testing. Following the same documentation,
I set up a Sandbox Tester in Apple Store Connect.
I saved a Public Certificate from the storekit configuration file in
the project.
I removed the local StoreKit configuration file from the scheme’s run
options (by setting to "none").
I added the following conditional compilation block to my store
manager:
#if DEBUG
let certificate = "StoreKitTestCertificate"
#else
let certificate = "AppleIncRootCertificate"
#endif
It is my understanding that an option to sign in with the SandBox ID should appear in device's App Store Settings after the first time I attempt to make a purchase when running on the device physically connected to my Mac.
This is not happening. Am I missing a step? One possible mistake I made was placing the (above) conditional compilation block in the wrong place. Can someone recommend the best place for this? The documentation says to paste it in with my receipt validation code. Another suspected oversight might be something else I need to do in Apple Store Connect. Not sure. Any help appreciated!
Addendum - I get this message in the console:
Error enumerating unfinished transactions for first transaction
listener: Error Domain=ASDErrorDomain Code=509 "No active account"
UserInfo={storefront-country-code=USA,
client-environment-type=Sandbox, AMSServerErrorCode=0,
NSLocalizedDescription=No active account}
I use ledger nano S for https://wallet.betanet.near.org/, and the ledger nano S successful configuration. after I delete all key from my account and just keep 1 Full Access Key(create by ledger nano S).
Now I can't add other fullaccess key. Whatever method is used.when I did: near login --useLedgerKey. the web verify page will show:
An error occurred while approving this action. Please try again!
When I did add Seed Phrase enable, on the [Enter the following word from your recovery phrase to complete the setup process.] page, When I confirm it in the Ledger it will show:
An error occurred while setting up seed phrase recovery. Please try again!
Actually , my ledger still will show confirm info:
DANGER: This gives full access to a device other than Ledger
when I make a transaction push √ button. it still show the error:
An error occurred while approving this action. Please try again!
I think it's a bug, when use just keep 1 access key form ledger nano S.
enter image description here
enter image description here
my account : catcatcat.test
This is probably an error on the NEAR Wallet side. If you don't mind me asking, what is your account ID? I can better understand what is happening by viewing the chain activity associated with this.
Unfortunately it takes time to get new app version published in Ledger Live (even in Developer Mode). First version that got published (1.0.0) has the bug with adding full access keys.
As far as I know this bug is fixed in latest version available here:
https://github.com/LedgerHQ/app-near/pull/2
Best shot for now is to try compiling it from source following instructions in README:
https://github.com/LedgerHQ/app-near/blob/6a8d3263896fdf65ac06961c6e7ed6a9912d5480/README.md
I have configured my sonar project view to receive a sonar PDF report however i am still not getting the same on email. Below are the steps I performed:
I have created a view where I have included my 6 projects. I gave
execute permission on view not on individual project.
I have set Executive Report option to come daily and provided email
id's to receive the pdf
I have set the Subscribe button which says "You are receiving PDF
reports by email every day."
Please suggest what is missing. Also the report doesn't include much details about the sonar code analysis. Is it possible to include below parameters:
Test Coverage
Unresolved Issues
I am not getting much help from Vendor on same.
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.
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).