apache / apache/cordova-plugin-inappbrowser
No redirect (http status 302) with Android 9
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
# Bug Report
InAppBrowser plugin does not redirect page
## Problem
Using Ionic5 with Cordova InAppbrowser we try to load a redirect page that is rendered from the origin page (https://iese-prueba.blackboard.com) to a redirected page where user enters user and password.
Redirection works fine in Android 8 but not in Android9 onwards, Redirect also works in a Chrome view in mobile and desktop version.
### What is expected to happen?
Redirect to the second page (as Android 8 does)
### What does actually happen?
Page is fixed to the first page, and redirection does not happen. No console error. No Android error (traced from Android Studio)
## Information
This is the code. it is almost 100% the example code from pluggin:
import { Component } from '@angular/core';
import { InAppBrowser } from '@ionic-native/in-app-browser/ngx';
@Component({
selector: 'app-home',
templateUrl: 'home.page.html',
styleUrls: ['home.page.scss'],
})
export class HomePage {
constructor(private iab: InAppBrowser) {}
openBlank() {
const browser = this.iab.create('https://iese-prueba.blackboard.com', '_blank');
}
}
### Command or Code
### Environment, Platform, Device
### Version information
## Checklist
- [x] I searched for existing GitHub issues
- [x] I updated all Cordova tooling to most recent version
- [x] I included all the necessary information above
Contributor guide
Research direction
Start with the InAppBrowser Android implementation and the openBlank() call that creates the browser with _blank. Reproduce the supplied redirect from https://iese-prueba.blackboard.com on Android 9 and compare it with Android 8. Done means the browser reaches the second page on Android 9 without breaking the existing Android 8 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100