Spotify | Repo for spotify project for capstone

So, I managed to do exactly what I wanted after 4 hours of tedious research.

Here's all the code:
Scriptable.sdef:

This is related to how gems are loaded by bundler. Bundler.require requires gems listed in Gemfile but does not require its dependecy. Its upto the library to require/load its dependency.

The mentioned issue happens when omniauth is not added explicitly to Gemfile, hence bundler does not require it.

But since omniauth-rails_csrf_protection assumes the ominauth is already required, it errors out when user only adds omniauth-rails_csrf_protection but does not add omniauth to Gemfile.

I have created a possible fix for the issue https://github.com/cookpad/omniauth-rails_csrf_protection/pull/13

UPDATE: The is fix has been merged in the gem repo.

Wait for a few minutes. Then run sudo snap remove spotify to remove spotify snap from your machine. Then again you can run sudo snap install spotify to install the spotify snap in your machine. Thanks.

I had the same error but with the typescript template

I made up this solution using RxJs. I hope it helps, give me a feedback if it works.

expand do recursive searchs and takeWhile control to requests only when Next isn't null. Reduce group all your tracks in an array. When you subscribe you have all the tracks available.

This is an example auth flow for spotify

https://github.com/yschimke/okurl/blob/0abaa8510dd5466d5e9a08ebe33a009c491749bf/src/main/kotlin/com/baulsupp/okurl/services/spotify/SpotifyAuthFlow.kt

There is no direct way to get a refresh token via the package. But there are other ways to get around this limitation. See bypass

Normally the Spotify auth api would include a refresh token, but this feature does not exist in the android sdk (cf: flutter package: #75 Android sdk: #12 #220 #225) although it is supported by the ios as well as the web sdk.

If the app is to be used only from ios or from the web, the maintainers of the flutter package would most likely accept a pr that exposes the refresh methods of the supported platforms even though it would bring little value.

If you are familiar with android development and the feature is important to you, you can try to integrate this feature into the android sdk yourself and then expose it in the flutter sdk.

Here this was already done in a fork:

• Repository

• Commit

The maker already opened a pull request but it has no responses yet (opend late 2018).

A way around this would be to store the username and password of the user on the device (or on the server) although this would be bad from a security standpoint.

Another inspiration might be this comment from an android-sdk user who routed authentication through his server.

Node https module have a separate option named protocol . So in the request option, you should not include https:// or http://.

Your options variable will become:

Profile, profile, profile. But the bottleneck is likely soptify's api. Whilst you can parallelise to speed up fetching, they won't thank you much for it and you will likely find yourself rate limited if you do it too much. So profile and see what is taking the time, but be prepared to cut back on your dataset.

Ask yourself what you can do to speed up the algorithm:

• can you just fetch the top N hits?
• do you really need all that data?
• is any data duplicated?

Even if data isn't duplicated, create a local cache, indexed by the track_id, and store every request in that. Rather than requesting from the spotify endpoint, look it up in the cache (store the data in another sqlite database, or another table in the same db). If nothing is returned, fetch, save the data to the cache, and then return it. That way:

• if you are doing redundant lookups, it will be faster.
• even if you aren't, you can re-run your code blazingly fast (at least as regards your current speed) if you change something and need to run the lot again.

So cache, profile, and look at your algorithm.