Thanks for the detailed update. I’ve been pouring through the logs and the code, and also run a sample migration and I can’t reproduce what’s going on for you.
Originally, I thought that sending a 0 percentage with
IN_PROGRESS status was going to cause an error, but that’s valid in the code and works for metm. You’re sending SUCCESS immediately after sending IN_PROGRESS, and I thought this might be an issue, but I can’t confirm as there are no errors in the logs.
What I do note is that for every test I’ve run, CCMA will show a green RUNNING status at the start which shows
onStartAppMigration() has been called, and because you aren’t seeing it I suspect there’s an issue with the registration part. But, and this is the weird part, I can clearly see you’re sending data through
createAppData() calls so I’m pretty sure
onStartAppMigration() is running correctly.
Let’s check a few items.
- Because you’re this far, you have the dark feature
migration-assistant.app-migration.feature on, do you also have
migration-assistant.app-migration.dev-mode in use as well?
- Did you complete App Assessment and mark the app as Needed in Cloud?
- And I think this will be the case, but is the app installed in Cloud?
- Do the server logs show a message starting with
Cloud app key is null for server app key ...?
I suspect now that because the server and cloud keys don’t match, then we still have a few gaps where they aren’t linked correctly in the code.
Let me know about the answer to those questions and we’ll continue on from there.