I am trying to use amplify authentication with my development. I have configured the staging environment on the AWS console, and I currently am trying to setup locally on my PC.
The command I was supposed to key into the terminal is:
amplify pull --appId dxxxxxxxxxxx --envName staging
And this is the result:
C:\Users\xxxxx\xxxxx>amplify pull --appId dxxxxxxxxxxx --envName staging
Found whitespace in your key name (use quotes to include) at line 2,8 >>><<<<<<< HEAD
"ver ...
Error: Found whitespace in your key name (use quotes to include) at line 2,8 >>><<<<<<< HEAD
"ver ...
at error (C:\snapshot\node_modules\hjson\lib\hjson-parse.js:41:11)
at keyname (C:\snapshot\node_modules\hjson\lib\hjson-parse.js:157:76)
at object (C:\snapshot\node_modules\hjson\lib\hjson-parse.js:353:15)
at legacyRootValue (C:\snapshot\node_modules\hjson\lib\hjson-parse.js:428:38)
at Object.<anonymous> (C:\snapshot\node_modules\hjson\lib\hjson-parse.js:454:23)
at Function.parse (C:\snapshot\node_modules\amplify-cli-core\lib\jsonUtilities.js:91:22)
at Function.readJson (C:\snapshot\node_modules\amplify-cli-core\lib\jsonUtilities.js:47:32)
at StateManager.getData (C:\snapshot\node_modules\amplify-cli-core\lib\state-manager\stateManager.js:215:56)
at StateManager.getProjectConfig (C:\snapshot\node_modules\amplify-cli-core\lib\state-manager\stateManager.js:95:25)
at Object.checkProjectConfigVersion (C:\snapshot\node_modules\#aws-amplify\cli\lib\project-config-version-check.js:33:63)
Anyone has any idea what did I do wrong and how do I fix it? Many thanks in advance! Cheers!
For me there was a conflict under amplify/.config that directory by default is not displayed in directory listings, (i.e. listing using the ls command or in your IDE). Check that out and see if it doesn't solve your issue.
Related
I am trying to simply upgrade the version of vue3 we are running at work from v3.2.31 to v3.2.40. However, when I do, I am now getting an error in the runtime-dom.d.ts
Below is a screen shot from the file with vue v3.2.31 installed.
Once I've run the "npm update vue --save" command, the file looks like this (v3.2.40)...
...and VS 2022 throws the following error when trying to build...
If I delete the line from my local copy of runtime-dom.d.ts, all works as before. My problem comes when deploying the solution to the development environment etc. The npm install step puts a version of the runtime-dom.d.ts that does still have this line.
I'd like to fix this without having to resort to hacking the runtime-dom.d.ts file if at all possible.
Many thanks in advance.
I am trying to configure the spark-submits to use JARs that are stored in artifactory.
I've tried a few ways to do this
Attempt 1: Changing the --jars parameter to point to the https end point
Result 1: 401 Error. Credentials are being passed like so: https://username:password#jfrog-endpoint. The link was tested using wget and it authenticates and downloads the JAR fine.
Error
Attempt 2: Using a combination of --packages --repositories
Result 2: URL doesn't resolve to the right location of the jar
Attempt 3:Using combination of --packages and modified ivysettings.xml (containing repo and artifact pattern)
ivy settings
Result 3: URL resolves correctly but still results in "Not Found"
After some research it looks like the error might say "Not Found" and the it looks like it has "tried" the repo, it could still very well be a 401 error.
Error
Any ideas would be helpful! Links i've explored:
Can i do spark-submit application jar directly from maven/jfrog artifactory
spark resolve external packages behind corporate artifactory
How to pass jar file (from Artifactory) in dcos spark run?
https://godatadriven.com/blog/spark-packages-from-a-password-protected-repository/
https://spark.apache.org/docs/latest/submitting-applications.html#advanced-dependency-management
You can use https://username:password#jfrog.com/rep, however you need to specify port.
https://username:password#jfrog.com:443/repo
I discovered this using Artifactory's "set me up" tool for package type Ivy. If you look in the resolver url it specifies the port.
BUMP: any thoughts or suggestions?
Building my web application has been throwing the following errors:
The command ""C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\signtool.exe" sign /a /t http://timestamp.verisign.com/scripts/timestamp.dll "application.exe"" exited with code 1
An error occurred while attempting to sign: application.exe
The specified timestamp server either could not be reach or
Based on this post, I added different servers with something like
signtool sign /v /td sha256 /tr "http://timestamp.comodoca.com/rfc3161" /fd sha1 application.exe
but my build still references the Verisign URL even after running this signtool catdb /r http://timestamp.verisign.com/scripts/timestamp.dll and signtool remove http://timestamp.verisign.com/scripts/timestamp.dll
Any ideas? Do I need to create a new certificate? Thanks in advance for help!
So I finally found what the problem was. There was a Build Event setting this reference to Verisign. Once I found it and updated, the build was successful.
The location of this is r-click on the project < select Properties < select the Compile tab < click button for Build Events...
Hope this helps any others.
I am trying to upload a dSYM file to Firebase using this command:
./Pods/FirebaseCrash/batch-upload -i ./Info.plist -p ./GoogleService-Info.plist ./service-accounts/mtb.json 78*****C-5**4-3***-***C-00*********7
But each time I run this, I get back the following errors
./Pods/FirebaseCrash/upload-sym-util.bash:377: error: symbolFileMappings:upsert: The uploaded file is not a valid Breakpad Symbol file.
./Pods/FirebaseCrash/upload-sym-util.bash:378: note: symbolFileMappings:upsert: The metadata for the symbol file failed to update.
I have tried this link https://groups.google.com/forum/#!msg/firebase-talk/4829Sp1_uKY/IEC_T4-VBAAJ but haven't had any luck as it errors out to
usage: batch-upload [-hv] [-p google-service] [-i info] service-account-file {mach-o file|uuid}
Can someone help me on this one please?
Thanks
Apparently this bug relates to batch-upload script having problems with archives, so you would need to patch it manually.
Try the following:
Change extract_symbols_and_upload "$EXE" "$ARCH" "$BUNDLE" to
extract_symbols_and_upload "$EXE" "$ARCH" "$BUNDLE/$BNDL_PATH"
The dump_syms utility understands dSYM bundles but not archives,
curiously enough. This fix will go out with the next release.
Source
Hi I'm having a million problems trying to publish my app to shiny.io.
Firstly, I have Rtools 3.2 installed in my computer and set to the Path, but it is not recognized in the registry. Nevermind, this code should fix it:
install.packages("installr")
library(installr)
install.Rtools(choose_version = FALSE, check = TRUE, use_GUI = TRUE,
page_with_download_url = "http://cran.r-project.org/bin/windows/Rtools/, keep_install_file=TRUE")
install.packages("devtools")
library(devtools)
devtools::install_github('rstudio/shinyapps')
Next, to deploy my app to my shiny.io account:
library(shinyapps)
shinyapps::setAccountInfo(name='xxxx', token='xxxxxxxxxx', secret='xxxxxxxx')
Then my app starts running in a browser, and I click publish to my shiny account. However, when the app is being deployed, it shows the following error:
Preparing to deploy application...Error: /v1/applications/ 400 - Validation Error
Execution halted
Any ideas what the problems may be? Thank you.
I had the same error returned. In my case the problem was the name of the app itself. Deployed apps must have names at least 4 characters long with no spaces.
Setting an application name solved this problem for me. My application directory contained a space.
deployApp(appName = "myapp")
I had the same problem, however, my app name was fine and even adding 'appName =' did not help. Just a side note that this issue came up because I changed the name of my folder in effort to change the name of my app in shinyapp.io
The only thing that worked for me is publishing through the "Publish" button of Rstudio on upper right. I would recommend publishing using that instead of command. You can select files you do not want to publish within the App folder and you can publish the app under a different name then your local name.
I also had similar errors and the issue was resolved after I changed the name of the directory that holds the "app.R" file from only 3 characters to more than 4 characters.