Skip to content
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

Unexpected behavior when using a null initialUrlRequest #1063

Closed
4 tasks done
RodXander opened this issue Dec 22, 2021 · 2 comments
Closed
4 tasks done

Unexpected behavior when using a null initialUrlRequest #1063

RodXander opened this issue Dec 22, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@RodXander
Copy link
Contributor

RodXander commented Dec 22, 2021

Environment

Technology Version
Flutter version 2.15.0
Plugin version 5.3.2
Android version 12
iOS version 15.2
Xcode version 13.2.1

Device information: Android Emulator Pixel 3a and iPhone 13 Simulator

Description

When no initialRequestUrl is provided to an inAppWebView or a HeadlessInAppWebView a callback to onLoadStop is triggered with an Uri for about:blank.

Expected behavior: When initialRequestUrl is null it should not trigger a callback to onLoadStop, since no url has been set.

Current behavior: A callback to onLoadStop is being triggered.

Steps to reproduce

import 'package:flutter/material.dart';
import 'package:flutter_inappwebview/flutter_inappwebview.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  String msg = "";

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: SafeArea(
        child: Scaffold(
          body: Column(
            children: [
              Padding(
                padding: const EdgeInsets.all(16),
                child: Text(msg),
              ),
              Expanded(
                child: InAppWebView(
                  onLoadStop: (controller, url) {
                    setState(() => msg = "onLoad: $url");
                  },
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}
  1. This
  2. Than that
  3. Then
@RodXander RodXander added the bug Something isn't working label Dec 22, 2021
@github-actions
Copy link

👋 @RodXander

NOTE: This comment is auto-generated.

Are you sure you have already searched for the same problem?

Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!

If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.

In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.

Following these steps can save you, me, and other people a lot of time, thanks!

Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants