Hi @Alberto Martínez

If your application on production environment and you don't have any issue so don't worry about the forge component version when you update your outsystems prod environment is auto Update

If your application in  Dev Environment so you can Simple update forge component and Refresh Dependency  so i will help in Future.

I have attached some Ref Link how to Update Forge as a Best practices so Please take as a ref:

https://www.outsystems.com/forums/discussion/94606/best-practice-and-procedure-for-rolling-back-forge-component-upgrade/

Thanks

Md Mansur

That change it´s needed to solve a bug that right now it´s raising it cannot read properties of undefined (reading 'open') and with the previous version it was working correctly.

Thanks

I'm facing this issue too.

Hi,
The newest version of the InAppBrowser plugin that the InAppBrowserEvents relied upon is very different and I will need to review the changes needed.

I suspect I will need to stop pointing to the supported InAppBrowser plugin in favor of the same plugin as before since I don't believe the new version allows us to expose the Events that this component exposed.

I'll deploy a new version once I figure out all the changes needed.

Hello guys,  

Is there a possibility that the InAppBrowserEvents plugin will be updated to the latest version of InAppBrowser (3.1.1)?

Thank you and keep the good work!

I'm facing the same issue.

Hi there,

I'm back just to let you know that after some tests I realised that the new InAppBrowser version (3.1.1) includes a webblock to do the same job that InAppBrowserEvents did, hence if you use the new version of InAppBrowser you don't need the InAppBrowserEvents plugin.

Cheers,

Hi, Thiago.

Actually, the block already exists on previous versions, but it only triggers the Load Event on first load.

Did it triggers the Load Event for every new URL InAppBrowser loads, in this new version?

Thank you.

Hi Alberto,

I got it. Unfortunately, I didn't test the mentioned use case.

I tested the other events and it works well.

It was a good idea to keep these event handlers together with InAppBrowser instead of separating them in another plugin (InAppBrowserEvents, in this case).

Good luck!

@Thiago Soares  , @João Barata 

Look like OutSystems doesn't have any plan to add the additional capability for handling events.

1) Trigger event for every url loads/redirect - useful for OIDC flow for copying data from URL.

2) Read data from address bar /URL.

Hi,

Any updates on this as version 2.4.10  is not compatible with MABS11. MABS10 will be not be available end May 2025.

Appreciate any help.

Hi Plugin Team ,

Please let us now if you have any plan for upgrading this components to adapt latest InAppbrowser Plugin  , This is critical to mobile application which uses the specific event handling technique provided by this plugin . Appreciate your communication on this so that app team can go for alternate path if this plugin is not going to maintain.

Hi, we have the same issue - 

"inAppBrowserRef is undefined"

Is there a fix on the horizon?

Without this, it renders our mobile-app unusable.

Are there any other suggestions, or replacements?

Would appreciate any information

Thanks

The InAppBrowserEvents plugin just exposes a few capabilities that the original InAppBrowser didn't and for that reason, it was using it as a core dependency.

However, with version 3.0.0, the underlying library of the InAppBrowser changed making it incompatible with the extra features of the InAppBrowserEvents.

As @David Vaello mentioned, we worked internally to try to come up with a solution, and in the meantime, that solution is to downgrade the InAppBrowser to version 2.4.10, which will restore the InAppBrowserEvents functionality while still being able to build your applications with MABS 11.

In the meantime, I'll continue with the path I was already taking of attempting to remove this dependency while still being able to use MABS 11.

Regards,