-
Notifications
You must be signed in to change notification settings - Fork 89
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
Search not working #22
Comments
Figured this out a while ago, forgot to update this. This can probably be closed, as it's not necessarily a problem with search, per se - the problem was, due to some lazy copy/pasting, I was using |
- propagates `SpotifyException` when dealing with `BundledPage` response - allows error provocation when using unti test
- adds more test asserts
I'll release a new package tomorrow, when I'm back on a real computer :) |
@mjuszczyk1 does the #29 PR solve this issue? @rinukkusu Can this be closed? |
|
I have spotify_io imported like
Copied the search from the examples directory on this repo
And I get a couple errors, the first one seems like a pretty simple fix:
[ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: type '_TypeError' is not a subtype of type 'SpotifyException' in type cast
- this error can be fixed by removing theas SpotifyException
cast. I first solved the issue by simply removing thecatchError
method, which revealed the second bug.I dug into this one a bit, but I'm pretty new to Dart/Flutter in general so I couldn't figure out a fix. I believe I traced it, at least, to a line in endpoint_paging.dart - specifically line 163. It seems the
_get
method is where this bug is actually being generated - I can get a breakpoint to hit onvar jsonString = await _api._get(path);
, but if I remove it and add one to the next line (var map = json.decode(jsonString);
), it never gets hit. I also can't get breakpoints to work in that_get
method, so I think this is pretty close to where the bug is coming from, but I'm currently stuck scratching my head.The text was updated successfully, but these errors were encountered: