supporting old app_links versions causes caught exception notifications for many users

[leewlms]

Bug report

• [y] I confirm this is a bug with Supabase, not with my own application.
• [y] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Bug occurs upon initiation

A clear and concise description of what the bug is.

Exception has occurred on line 198 (supabase-flutter/packages/supabase_flutter/lib/src /supabase_auth.dart)
NoSuchMethodError (NoSuchMethodError: Class 'AppLinks' has no instance method 'getInitialAppLink'.
Receiver: Instance of 'AppLinks'
Tried calling: getInitialAppLink())

To Reproduce

Run app

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Initialize supabase

Expected behavior

Supabase authentication

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: [iOS]
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

Add any other context about the problem here.

[Dev-Adnani]

Facing Same Issue

[pawel221]

I have same problem

[borisandcrispin]

Same issue

[Hallidayo]

Hi, I've moved this issue over from the supabase repo as its flutter related.

[Vinzent03]

This is effectively a duplicate of #941, but since this is bad for developer experience when having the stop on caught exception setting turned on in vscode, I would propose we do a breaking change and bump the app links dependency. This way we don't have to support both apis.<
@dshukertjr What do you think?

[HektorCyC]

Im able to reproduce the bug.

[Delthoid]

Update on this?

[btrautmann]

It's worth saying that this isn't just a DX issue, at least AFAICT. It was happening to me and I could not figure out why my app kept freezing on the splash screen. After finally realizing I did not have "All Exceptions" checked in the debugger and checking it, I saw that this was the issue. Obviously I should have a more resilient main method but I just wanted to point out that at least AFAICT this can impact runtime behavior negatively.