Hi @jessicagarson, have you received any update on this issue? The problem persists and we still don’t have access to the app’s administration screens.
Thanks, @jakepeyser. I was still waiting to hear back but escalated to a different pathway.
Thanks for persisting, will stay tuned.
Do you know what level of access you have? This might be an issue with receiving this standalone App as an essential developer (we didn’t allow essential developers to manage standalone apps, but they might show up if you happen to own one). If you have essential access applying for elevated will allow you to regain access to this App, if you are approved.
Yes, it looks like I have essential access so maybe that is the issue. I can apply for Elevated Access and see if that resolves the issue, assuming I am approved. Let me apply and check back in once that process is complete. Thanks Jessica.
1 Like
Let’s start there and let me know how it goes.
That did it! Thank you so much, Jessica.
One follow-up question: Is it possible to move this app under our Tree project? We’d like to use this as our production application and create an additional two for staging and development purposes.
Thanks, @jakepeyser. If you go into the project and delete the new App you created, you can add a new App and this App can be a standalone App.
I’ve been able to create the new apps for Dev and Staging. When I attempt to add the existing standalone app to the new project, I get the below error: " Your changes couldn’t be saved. This client app has already been added to your project.". It looks like 400 status code. The app continues to remain as a “Standalone app” in the navigation and cannot be found under the Tree project. Might this be a bug?
1 Like
Hi @jessicagarson, any guidance on this? I’m happy to create a support ticket for the remaining issue if you think that is a better course of action
Have you had anything back on this? Trying to access old standalone apps I made pre-v2 and I can’t get into them either. 
@LaimMcKenzie Jessica’s suggest solution above re: applying for elevated access resolved my initial issue. I am just trying to figure out how to move the app to my project at this point, but it is now accessible
2 Likes
Hi @jakepeyser, I took a short break away from this forum but just getting back here. Is this still an issue? If so, what’s the current App ID? Thanks again!
@jessicagarson All good thanks for jumping back in! It is still an issue for app ID 23861329
Just sent this to the team, I’ll let you know when I hear back.
1 Like
Our team has found that the issue has been caused by this app being associated to a project belonging to the previous owner (which can’t be seen by the new owner but still cause the issue). We’re working on removing the association, but we are also aware that this is probably an edge case that can come up when apps transfer owners.
I’ll let you know when we have a fix.
1 Like
This issue should be resolved - can you confirm?
Yes it is resolved! The project is now set up as expected, thank you to you and your team discovering and resolving this edge case. I appreciate your help through all these steps @jessicagarson
1 Like
Thanks so much! Also, thanks for bearing with me while I took a break from this forum. I’ll also try to make sure in the future we have better internal coverage of this forum when this sort of thing happens.
1 Like
system
Closed
#23
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
