Ionic-native InAppBrowser, pass url parameters to app


The particular authentification method that I’m using in my app requires the inAppBrowser to open an external URL which will contain URL parameters that need to be passed into the app.

Does anybody know how to go about this in v2?



So you want to get back URL params from the InAppBrowser back into your app?

Precisely :slight_smile:

ionViewWillEnter() {

const browser = this.iab.create('', '_blank', {
  location: 'no',
  zoom: 'no',
  data => {
      let url = data.url;
     (here you do whatever you want with the url) alert(url);


Dunno if this helps, for me i used it to grab URL and use a condition when the user visited a specific URL to trigger a function. Maybe also you can manipulate the URL and grab the params you need.

1 Like

Thank you! I’m going to try it out and see if it works for me.

of course you need to declare in your constructor “private iab: InAppBrowser”, and import in your declarations import {InAppBrowser} from “@ionic-native/in-app-browser”

1 Like

I have a similar issue, I fetching the url data on loadstop event, and on exit event I am calling a local service where I have to pass that fetched data. But in the exit event I am not able to access the url data. I have no idea why this is happening. Below is my code

public office365Login(){ 

 let browser = new InAppBrowser("" +SvcConstsService.TENANT_ID+ 
            "/oauth2/authorize?response_type=code&client_id=" + SvcConstsService.CLIENT_ID +
            "&resource=" + SvcConstsService.GRAPH_RESOURCE +
            "&redirect_uri=" + SvcConstsService.REDIRECT_URL,'_blank','location=no');

                 console.log("code_token ",this.code_token);
                 console.log("session state ",this.session_state);
          // code_token and session_state is the data I am getting from url
           // the fetched data is passed to the below method, but not able to access it.
1 Like

Hi, do you have found a solution?

looks like his loadstop and exit handlers had different ‘this’ references:

.subscribe(()=>{}) vs. .subscribe(function(event){})

1 Like

On loadstop() event if you are getting data from the url, then store that in local storage, and on exit event fetch that data from the local storage, and make a service call to the backend. This works for me.

browser.on("loadstop").subscribe(function (event) { localstorage.setItem('foo','foo'); localstorage.setItem('bar','bar'); }

 browser.on("exit").subscribe(() => { = localStorage.getItem('foo'); = localStorage.getItem('bar');
     // service call method()


Hope this helps .

1 Like

You coul also change the loadstop handler to be an arrow function as on exit (and acually give a variable for the on at exit to make this more consistent):


Then it should be more consistent, as @Justin_H already said.

You saved my life, thank you!