Currently, the classification as "Suggestion" does not quite do justice to the content of the issue. We fought to have the status changed from unimportant to critical. After nearly two years since the initial issue (FRGE-1145) was opened, this is a significant setback. All options available in Confluence Cloud for Connect should also be available for Forge. In addition, this feature is already available in Jira Service Management with Forge. Therefore, I believe it is not a 'Suggestion' but rather a missing piece of basic functionality.

This is a barrier to using Forge, and therefore the classification of the issue should be reviewed and adjusted accordingly.

Aside from the underlying issue, it was also nearly impossible to find information about the current restriction. I had already suspected something like this, but without opening the ticket that led to this issue report, I wouldn't have been able to confidently identify the cause of apps not appearing for guest accounts. Additionally, the error message is not helpful at all. 

Perhaps adding a note to the documentation and/or improving the error message would be helpful until the issue is fully resolved.
Thanks in advance

LIke David, this will block some of our apps adopting Forge due to having to remove functionality for existing customers. 

Why has the original issue been resolved without completion?

It's a problem with lack of functionality in Forge, not some “nice to have” suggestion for a new Confluence feature.

This issue is a blocker for me to migrate apps from Atlassian Connect to Forge.