Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amplify Predictions Parameters: [access, format, identifyDoc] must have values #13320

Closed
3 tasks done
rpostulart opened this issue Oct 8, 2023 · 3 comments
Closed
3 tasks done
Labels
duplicate If marked with duplicate, issue will be closed & original will be added for traceability pending-triage Issue is pending triage predictions Issue tied to the predictions category transferred This issue was transferred from another Amplify project

Comments

@rpostulart
Copy link

rpostulart commented Oct 8, 2023

Before opening, please confirm:

JavaScript Framework

React Native

Amplify APIs

Predictions

Amplify Categories

predictions

Environment information


  System:
    OS: macOS 14.0
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 62.57 MB / 16.00 GB
    Shell: 5.0.11 - /usr/local/bin/bash
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 117.0.5938.149
    Safari: 17.0
  npmPackages:
    @babel/core: ^7.20.0 => 7.23.0 
    @react-native-async-storage/async-storage: 1.18.2 => 1.18.2 
    @react-native-community/netinfo: 9.3.10 => 9.3.10 
    HelloWorld:  0.0.1 
    amazon-cognito-identity-js: ^6.3.6 => 6.3.6 
    amazon-cognito-identity-js/internals:  undefined ()
    aws-amplify: ^5.3.11 => 5.3.11 
    aws-amplify-react-native: ^7.0.7 => 7.0.7 
    expo: ~49.0.13 => 49.0.13 
    expo-camera: ~13.4.4 => 13.4.4 
    expo-file-system: ~15.4.4 => 15.4.4 
    expo-image-manipulator: ~11.3.0 => 11.3.0 
    expo-status-bar: ~1.6.0 => 1.6.0 
    react: 18.2.0 => 18.2.0 
    react-native: 0.72.5 => 0.72.5 
    react-native-quick-base64: ^2.0.7 => 2.0.7 
  npmGlobalPackages:
    @aws-amplify/cli: 12.6.0
    corepack: 0.17.0
    eas-cli: 5.4.0
    expo-cli: 6.3.10
    npm: 9.5.1



Describe the bug

When created a new expo project, add aws amplify, add auth , then do amplify push.
After that add amplify identity text and do amplify push again, I get:

`
🛑 The following resources failed to deploy:
Resource Name: predictionsidentifyText4d315636 (AWS::CloudFormation::Stack)
Event Type: create
Reason: Parameters: [access, format, identifyDoc] must have values

🛑 Resource is not in the state stackUpdateComplete
Name: predictionsidentifyText4d315636 (AWS::CloudFormation::Stack), Event Type: create, Reason: Parameters: [access, format, identifyDoc] must have values, IsCustomResource: false
`

Expected behavior

I expect that it will deploy the predictions stack.

Only when adding these keys manually to:
parameters.json in the predictions folders it will deploy:

"identifyDoc": "ID_TEXT",
  "format": "PLAIN_TEXT",
  "access": "AUTH"

Reproduction steps

see above

Code Snippet

(https://github.com/rpostulart/nbCamera)

Log output

// Put your logs below this line


aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

@rpostulart rpostulart added the pending-triage Issue is pending triage label Oct 8, 2023
@nadetastic nadetastic self-assigned this Oct 9, 2023
@nadetastic nadetastic added the predictions Issue tied to the predictions category label Oct 9, 2023
@nadetastic nadetastic transferred this issue from aws-amplify/amplify-js Oct 10, 2023
@nadetastic nadetastic added the transferred This issue was transferred from another Amplify project label Oct 10, 2023
@nadetastic nadetastic removed their assignment Oct 10, 2023
@nadetastic
Copy link
Member

Hi @rpostulart transferring this issue over to the CLI repo for better assistance.

@ykethan ykethan added the duplicate If marked with duplicate, issue will be closed & original will be added for traceability label Oct 10, 2023
@ykethan
Copy link
Member

ykethan commented Oct 10, 2023

Hey @rpostulart, thank you for reaching out. The issue is currently being tracked on #12159.
As you have pointed out, adding the missing parameters to parameters.json and running push should mitigate the error.
Closing the issue.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate If marked with duplicate, issue will be closed & original will be added for traceability pending-triage Issue is pending triage predictions Issue tied to the predictions category transferred This issue was transferred from another Amplify project
Projects
None yet
Development

No branches or pull requests

3 participants