Embed Sign-In Required Apps in Google Sites

  1. No plans for custom domains support at the moment. we could easily extend this in the future.

  2. Yes. With this feature, we will support read-only full-page embeds and our long term plan is to allow for intractability in full-page embeds once we have a longer-term fix for the clickjacking issue in place (which will be several months into the future).

7 Likes

The edit (pencil) option isn’t available after embedding a website via URL, only open in a new window and trash.

Thank you. This worked for me when using the normal in-page embed. Sometimes I needed to adjust dimensions.

Thanks for the reply @nico ! Custom domain support would be a huge milestone in my humble opinion. I have been waiting for this since the start of my AppSheet journey.

3 Likes

@nico thanks for the pointers but I still cannot get any app to work while embedded - I have tried:

  1. Accessing as a viewer so no edit icon (not sure how usable this will be if all site editors will get blocked from using the embedded app because of the edit button?)
  2. Changing the size
  3. Removing the reauthenticate box
  4. Added a section beneath the embed so the information icon will sit over that instead or the embedded app.

Here’s a video showing the issue with all your suggestions inplace:

As yet I have not seen anywhere an example of a working, embedded AppSheet app in a Google Site: do you have an example to show?

I cannot find any way to make an app usable, so in its current state it’s unusable for me. I’ll happily take more advice if you have any, or if you can actually show a worked example of you successfully embedding and using the app, that may show where I’m going wrong.

I hope you can make it work better in the future, but it’s a non-starter at the moment.

1 Like

Are there any plans to bring this to Non Sign-In Required Apps in the near future?

@Karimmc2 non-sign in apps are available now: you need to be paying for an Enterprise Plus licence to get it.

3 Likes

It looks like this full page embed edit button may be part of a feature rollout that’s isn’t available to all users yet. Hopefully it rolls out soon so you at least have the workaround (the rollout is owned by the Google Sites team so I have no control over it).

For reference here is how it looks like in two different accounts for me:

|


|

|
| - | - |

Even once that’s rolled out, the full-page embed will not be interactable anyways, because of the info button overlay, so I’d recommend using the embed from the insert menu and making it as large as you can unless you only need read-only app data.

  • (Supported) From “Insert”:

  • (Not supported) From pages:

Working on updating documentation to reflect this.

3 Likes

Thanks for the video again. Seems like you have that setup in the best way I know how. Here is a video of how it should work.

For reference, security team required me to use IntersectionObserverV2 which is detects visibility and is allowed to report false negatives by design (to be conservative) as protection against clickjacking. Depending on the device / screen resolution / operating system, it may be report visibility checks far too aggressively. From my own testing, I’ve noticed different behaviors on different devices - but it never failed completely like this.

To fix, I think I can justify skipping this visibility check specifically for embeds under sites.google.com, I just need security team’s input on that. If that’s approved, it should make the feature at least useable on your device.

I appreciate the comment, it helps escalate issues internally. I’ll update this comment thread once that suggested fix is approved / denied / merged.

2 Likes

Thanks @StephenHind , I will try the embeded feature with a non-sing in app

@nico thanks for the video of how it should work: that’s what I was hoping for.

Do you have a video of someone actually embedding it?

I’m a bit confused about skipping the clickjacking protection in sites: you can only embed a signed-in required app in Google Sites anyway (it’s not allowed elsewhere). Google Sites does not allow the editor to overlap, overlay, or obstruct content, it’s simply not possible, so that should never have been a worry with Google Sites. It would be advisable to remove clickjacking for Google Sites, so that it doesn’t get triggered for the edit and info button overlays, that the site owner/edit can do nothing about (we cannot remove them, only the Google Sites team).

Finally, after your “Depending on the device / screen resolution / operating system, it may be report visibility checks far too aggressively” comment I have found the issue with the embed: it’s not working on any of my Chromebooks! It’s working on Chrome in Windows 10, but not ChromeOS - you may want to look at that with some priority as I’m sure Google wants AppSheet embeds working on its own OS! I don’t have macOS handy to test it on and I have been working solely on Chromebooks (and Chromeboxes) for the past 12 years, so please get this working on ChromeOS!

3 Likes

Yes, I agree with what you said - Google Sites doesn’t allow for custom CSS or scripts. I made that argument with the security team and got approval to allowlist Google Sites specifically! :slightly_smiling_face: There’s some technical details on why this was a harder decision than it may seem, but I’m glad they’re okay with that since it makes the feature work way better.

Starting with today’s release, intersection observer check are no longer required and I expect it to work on all your devices now including Chromebooks.

Once again, thanks for the feedback!

1 Like

@nico many, many thanks for the responsiveness! I can confirm it’s working on the Chromebook even with the Edit button over the embedded app:

Just need it working on a full-page embed and we’re golden!

1 Like

Hi イルカのえっちゃん

I have noticed that even the floating button in the preview mode are also triggering the intersection observer , I tried publishing my site and preview it from there and the app embed is interacting just fine

Preview

2 Likes

Hi イルカのえっちゃん ,

Please try again now. We’ve been able to remove the IntersectionObserver running at least for sites.google.com so you should no longer run into this issue.

Thanks for the video!

2 Likes

Thank you!
I finally found the cause of this phenomenon and solved it.

2 Likes

@nico

Im still puzzled how this new feature would work.

I embedded app with full screen (as I assume, as there is no vertical/horizontal scroll bar inside the embedded app), but once we click anywhere inside the embedded app, it always sees windows to guide me to open the app in other tab.

As you see below image, the app is embedded with full screen mode. No scroll bar for both vertical/horizontal.

Once we click anywhere inside the app, the pop up window always being thrown.

“Cant interact with app when partially visible. To interact with this app, scroll the view entire app on screen, resize the app to fit your screen, or open in new view.”

This error/guide message is giving me more confusions to be honest with you.

Yes, I did follow what this message says, but still no effect.

3 Likes

@Koichi_Tsuji try using it from the published site and not the preview: it doesn’t work in the preview.

3 Likes

@StephenHind

Oh! thank you for your advice. Yes, it did work after publishing the site. Thank you again.

3 Likes

So far I haven’t been able to use this feature in the published site. In the site editor it works just fine but when accesing from the published site I get an “www.appsheet.com refused to connect” error message.

What could it be? Am I doing something wrong here?

1 Like