[iOS] Branch SDK Listener Fails to Receive Immediate Session Data When App Opened via Branch Link

[chiragvorasav]

To Reproduce
Steps to reproduce the behavior:

1. Update the Flutter SDK to version 3.19.3 and the flutter_branch_sdk package to version ^8.2.0.
2. Initialize the Branch SDK in the main.dart file using the method:

   await FlutterBranchSdk.init(enableLogging: false, disableTracking: false);

3. Set up the listener using:

   FlutterBranchSdk.listSession().listen(...);

4. Click a Branch link from the Branch dashboard, e.g., in Slack.
5. Observe that the app opens but does not receive session data immediately. Instead, you receive:

   {+is_first_session: false, +clicked_branch_link: false}
   

6. Put the app in the background and then bring it to the foreground. Only then does the correct session data response arrive.

Expected Behavior
When the app is opened via a Branch link, the listener should immediately receive the correct session data containing the clicked link information.

Screenshots
A screen recording of the issue is available https://drive.google.com/file/d/1AuEbJy2l-8amhSeyT7SKhWLfAZcbkO6g/view?usp=drive_link

Mobile (Please complete the following information. Remove if not Mobile):

• Flutter version: 3.19.3
• flutter_branch_sdk version: ^8.2.0
• OS: iOS 17 (affects all tested iOS devices, e.g., iPhone XR)

Additional Context

• The bug is causing delays in receiving Branch link data, impacting the app's functionality and delaying the release process.
• Expected the FlutterBranchSdk.listSession() to provide the session data immediately after opening the app through a Branch link.
• Could you please provide a solution or guidance urgently?

---

Let me know if you need further clarifications or updates!

[chiragvorasav]

Hello,

we are waiting for your response.

[RodrigoSMarques]

I can't reproduce your problem.

It's working normally here, so there's no answer for now.

[chiragvorasav]

I am currently facing the issue still . Earlier, I encountered issue #365. Could you please suggest a solution or workaround for this?

[RodrigoSMarques]

#365 is not an issue. It is a code PR between branches, after a new release

The problem you are reporting existed in version 7.x.

In version 8.x, after testing with developers from several projects, it was considered resolved.

I ran several tests with my project and I can't reproduce the problem. In all executions, the application opened and was able to access the deeplink data.

There is an issue where a developer is having problems due to a conflict with another package. After removing the conflicting package, the error stopped occurring.

There is another issue, where the project was configured with the test keys and the deeplink was with the production key.

Without knowing your project, I cannot reproduce it.

Still evaluating.

[chiragvorasav]

Sorry, my mistake. Could you please check this?

"#355"

#355

[RodrigoSMarques]

Yes. But note that he was using version 7.x, which as I reported above had a problem.

The solution for him was to update to version 8.x.

You will find other issues and in all of them the guidance was to update to version 8.x.

Since there were no other comments on the issue, I understand that changing the version from 7.x to 8.x solved the problem.