I have moved my app up to Heroku for its production home. I have created new instances and installed my app successfully several times.
- IMPORTANT NOTE: I only create a few new instances so I could ensure that the install worked successfully from a brand new instance that had never had an install of my app to it.
In my main stage instances, I have installed, uninstalled and reinstalled my 10+ times with no issues. So I cannot reproduce the issue that Atlassian is seeing. I could this thread and removed the code as specified: 401 (Unauthorized) after moving to Heroku. However, I am still successfully installing my app.
To this point, Atlassian support has not offered any steps to try and reproduce what they are seeing. I’ve worked with Heroku support and they have assured me that this issue does not sit on their side.
Finally, I have gone back through all of the steps I used to generate my ACE-based app, the installing it from the Marketplace steps and the Heroku setup steps and everything looks to be fine. I was wondering if I missed a flag or maybe needed to reconfigure my atlassian-connect.json or config.json files but again, according to the documentation I used to reach this point, everything looks good and is working just fine for me. But right now this is holding up my app from being approved to go public in the Marketplace so I thought I would reach out to the community for help. Please note, this is also my first app and first time through the approval process.
Anyway, has anyone else experienced this scenario where it works for you but not Atlassian? What are some other things I should check? My localBaseUrl in the config.json file is currently set to https://instance-auditor.heroku.com. If this should be set to something else, please advise but I have not found any documentation stating otherwise.
As always, thanks in advance for any assistance provided.