Troubleshooting the migration
|
Problem |
Recommended solution |
|---|---|
|
|
Run the script from the project root where app/build.gradle or your application module build file is stored. |
|
Prompt |
Network access to the BlackBerry Maven repository is required. Whitelist *.blackberry.com for your agent or network proxy, then run |
|
The project does not use a Git repository. |
The migration process can continue without Git. Git is optional, but is recommended for rollback and audit: |
|
Prompt |
Grant your AI coding agent file read, file write, shell execution, and full network access permissions, then run |
|
Prompt |
Review |
|
Your agent invents APIs that do not exist. |
Instruct the agent: "Use only APIs from the steering files. Do not invent APIs." |
|
The build fails after migration. |
Run |
|
|
Secure APIs were called before |
|
|
An activity is missing |
|
An |
A |
|
Validation fails on a specific phase. |
Check |
|
validate.sh flags Room, OkHttp, or direct |
Run the relevant migration prompt (04, 05, or 06) again, or add the domain to |
|
Prompt 10 reports EXECUTION PLAN GATE FAILED. |
An applicable domain does not have a completed prompt or a signed-off deferral. Run the listed prompts again or add |
|
Your agent guesses values for |
Stop the migration process. You must define the values. For more information, see BlackBerry Dynamics SDK migration toolkit: Prerequisites and considerations. |
|
settings.json does not match bootstrap.json. |
Run prompt |
|
migration-report.json is missing fields. |
Run prompt |
|
The report viewer does not display any information. |
Run the following to validate the JSON: |
|
|
Run the offending prompt again. record-prompt-execution.sh is idempotent and should replace the prior entry. |