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

No response received from FlutterBranchSdk.getShortUrl #415

Open
ihr1337 opened this issue Jan 22, 2025 · 3 comments
Open

No response received from FlutterBranchSdk.getShortUrl #415

ihr1337 opened this issue Jan 22, 2025 · 3 comments
Labels
under analysis need more analysis

Comments

@ihr1337
Copy link

ihr1337 commented Jan 22, 2025

Keep the template and provide all requested information:

Describe the bug
Response from await FlutterBranchSdk.getShortUrl is received only on first url generation, after I have to restart/rebuild the app.
No errors, method, where I use await FlutterBranchSdk.getShortUrl just stops and doesn't go further after generation attempt.

To Reproduce
Steps to reproduce the behavior:

  1. Trigger await FlutterBranchSdk.getShortUrl for second or more time.
  2. Put breakpoint at the vars/methods after await FlutterBranchSdk.getShortUrl

Expected behavior
Url is generated and share modal shown.

Screenshots
Image

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

  • Flutter: 3.24.3

  • flutter_branch_sdk version: 8.3.2

  • OS: iOS 18.2

  • Device: iPhone 12 Pro

  • Additional context

Url generation was working fine past week, I didn't change nothing in the code and today noticed the issue mentioned above.

@ihr1337 ihr1337 added the bug Something isn't working label Jan 22, 2025
@RodrigoSMarques RodrigoSMarques added under analysis need more analysis and removed bug Something isn't working labels Jan 24, 2025
@RodrigoSMarques
Copy link
Owner

open the "Android" folder of your project in "Android Studio", run it in debug mode and check if any error messages are displayed in Logcat.

Without any error indication it is impossible to determine what the problem might be.

@ihr1337
Copy link
Author

ihr1337 commented Jan 27, 2025

I'm sorry, forgot to mention that issue persists for iOS only, what's the way to get error logs in this case?

@RodrigoSMarques
Copy link
Owner

I'm sorry, forgot to mention that issue persists for iOS only, what's the way to get error logs in this case?

open the "iOS" folder of your project in "Xcode", run it in debug mode and check if any error messages are displayed in Logcat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
under analysis need more analysis
Projects
None yet
Development

No branches or pull requests

2 participants