I have run into a scenario where the embedded canvas app is not showing in other environments correctly after deployment, with error message the app is not shown correctly please ask the app owner to grant you sufficient permissions, so I followed the below steps to troubleshoot my issue:

1. Shared the canvas app after it has been deployed to everyone.. This did not fix the issue
2. Made sure that the security roles assigned to me has the permission on canvas app through customization..This did not fix the issue
3. While I was going through this article for troubleshooting the embedded canvas apps I came through this point below:

The App Name property value is missing or is incorrectly defined

To resolve this issue, choose the correct option:

• Managed solutions: If the solution was imported into an environment as a managed solution, follow these steps:
  1. Sign into Power Apps and go to the development environment where you originally created your embedded canvas app. This is also the environment where the solution was exported.
  2. Open the unmanaged solution that includes the canvas app, and then find the canvas app in the list of solution components. Copy the canvas app Name exactly as it appears in the components list. For example, contoso_flooringestimatesapp_624d7. 
  3. In the same solution, edit the model-driven app that has the embedded canvas app control, and then set the canvas App Name to the embedded canvas app control using the value from the previous step. More information: Add an embedded canvas app on a model-driven form
  4. Export the solution from the development environment and then import the solution into your target environment.
• Unmanaged solutions: If the solution was imported into an environment as an unmanaged solution, edit the model-driven app, that has the embedded canvas app control, and then follow similar steps as described for a managed solution to set the canvas App Name property.

So I simply went to my model driven form and changed the app name to the app name similar to the above screenshot and that did the trick.

Happy Low Code debugging