-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would scope_extensions handle this scenario? #46
Comments
Yes by virtue of extending the app's scope to include that other origin. |
@JudahGabriel how did you manage to make 1-5 work? We have a multi tenant web application for which we would like start develop mobile apps using pwa. Of course we would like to have only one app, not for every tenant. We have the root domain that is being used as a starting point and it can direct users to their instances. This works fine for ios using allowedOrigins, works fine from android using additionalTrustedOrigins, but I cannot make it work for windows. There is no such configuration option for windows and I get the address bar for my domains outside the root domain. I was trying to use url_handlers and scope_extensions in my manifest, but none of that worked out. Can you please help me with this? |
We haven't made that scenario work, because |
We have a multi-subdomain internal web application (4 businesses with one subdomain each) under a domain that manages the users and sessions. Example:
We're looking forward to being able to install a PWA for the Login app and redirect our users to each business app without them noticing. We're hopping |
@sertxudev we are trying the same scenario and also hope that scope_extensions will solve our issue in the future. |
A team building a large productivity PWA is encountering the following issue. Will
scope_extensions
support it?That last step is the issue. They want users who click that push notification to open in the installed PWA. Instead, today, it's opening in a new browser tab.
Will
scope_extensions
support this scenario?The text was updated successfully, but these errors were encountered: