Common and Known Issues

• Images won't load

This is often an unfortunate side effect of being connected to the host device via wifi. Since the guest's Wi-Fi connection is being occupied connecting them to the host device, the guest device isn't connected to the Wi-Fi network and thus cannot load images from the internet. Switching to only Bluetooth connections would greatly limit party size, so it isn't a viable solution. At the moment, this is not an issue we are working on fixing.

• Spotify suddenly stopped playing music even though there are still songs in the queue

Sometimes, Spotify will fail to execute/miss the command to play the next song and will be left playing no song. A work-around has been rigged to restart the song if the host presses pause and then play again in the partyq app. If this does not work for you, please send us a bug report.

• I was randomly disconnected from the party

Assuming you were still within range of the party, if you were a guest and were connected via Bluetooth, it's possible that the host device had reached its maximum number of Bluetooth connections (usually 3-4 in practice), and had to boot a connection. Preferring a Wi-Fi connection to the host may remedy this issue. If your problem was different, please contact us and provide as much detail as you can about the events leading up to your disconnect so we can do our best to find the issue.

• Song search failed with an error

The most common cause of this issue is that the host device (which performs your song searches for you and then sends you the results) has no internet. This can happen briefly after the host makes a Wi-Fi connection to a new guest.

Alternatively, Spotify could be temporarily blocking searches if too many are being made by partyq in quick succession.

• Guest can't find the party even though they typed the correct party code

Be sure that you are close enough to the host; within 100 meters and/or you are connected to the same Wi-Fi network and router as them.

If that wasn't your problem, it may just have taken the guest device so long to detect the host's party (20+ seconds), that partyq incorrectly assumed that there was no party matching the input code and stopped searching. Usually, trying again will result in finding the party much more quickly. If you encounter this issue consistently, let us know; we may consider increasing the maximum amount of time partyq will search for a party.

• When a new song starts, sometimes a bit of a different song plays for a second

This is due to the current limitations of the Spotify developer SDK which partyq uses to play music; it currently does not notify partyq when a song ends, and will automatically start playing another (random) song. partyq deals with this by checking if the currently playing song is the song we expect it to be (the next in the queue), if not we will tell Spotify to play the correct one. A little lag in the process is what leads to the start of a random song occasionally being heard between songs.

The Spotify developer SDK is still in beta, so it is possible that updates could allow this issue to be fixed or further mitigated in the future.