Nevertheless, the symptoms on my GNote2 is not as balck&white as you seem to describe it regarding Android 4.4...
As you can see on the screenshot attached, I've tons of folders and files stored by Spotify on my extSD ! :)
And I do understand that... I may found an easier (temporary) solution.
Wipe Spotify data, launch it without any external SD so Spotify store files in the internal memory then reinsert the SD card.
I've never heard about that before... Thanks for sharing this article as it might be a huge problems for tons of developers.
However, what's strange is I can normally access my external SD with ES Explorer or ADB and I can copy, push and create folders and files on my external storage.
Also, I am currently developing an Android app that is only dealing with external SD card for app storage using the permissions READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE without any problem on my device, running 4.3 or 4.4.
That is why I am suspecting an error on the Spotify-side... Besides, I saw the same error on a Samsung official 4.3 ROM a few days ago (see my first post).
Finally, using DDMS, I have some errors coming from the Spotify client but nothing seems to be directly related to my issue (the only exception is a HTTPS certificate exception, see below)
02-16 10:57:33.600: W/System.err(17953): javax.net.ssl.SSLException: hostname in certificate didn't match: <market.spotify.com> != <api.tunigo.com> OR <api.tunigo.com> 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:185) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:114) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:95) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:388) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:165) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555) 02-16 10:57:33.605: W/System.err(17953): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487) 02-16 10:57:33.605: W/System.err(17953): at com.b.a.a.c.run(SourceFile:54) 02-16 10:57:33.605: W/System.err(17953): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422) 02-16 10:57:33.605: W/System.err(17953): at java.util.concurrent.FutureTask.run(FutureTask.java:237) 02-16 10:57:33.605: W/System.err(17953): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 02-16 10:57:33.605: W/System.err(17953): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 02-16 10:57:33.605: W/System.err(17953): at java.lang.Thread.run(Thread.java:841)
I've never heard of that issue and actually never experienced it. Besides I've some apps installed on the SD card or apps storing obb or other files on my SD like the camera app and no issue so far. I'm running a custom 4.4 CM 11 based Rom. BTW I'm a Spotify Android beta tester. Antoine.
Hi, OK I've a SanDisk 32Gb class 10/UHS-1 microSD. I've backed up all my data, run a couple of disk integrity tests without errors. Then I reformatted the card directly on my device running the legacy Android formatting tool. I've no issue with any app dealing with external SD card except from Spotify. I still get the error message but I see the Spotify storage folders normally using ES Explorer. It is really seems that the issue is on the Spotify client side. Any other test I can run to be sure? Or any logs I could retrieve from Spotify to check potential errors? Thanks Antoine Galaxy Note II GT-7100 Spotify v. 0.7.6.344
Device : Galaxy Note II (GT-N7100)
SD Card : 32Gb Class 10
Android version : 4.3 - N7100XXUEML3
Spotify version : 0.7.5.698
Internal storage : 9,63Gb/10,44Gb used
SD Card storage : 15,0/29,71GB used
Action : request for synching 2 playslits offline (~400 songs)
Expected behavior : offline sync on SD Card normally (chacked with file explorer, Android/data/com.spotify.mobile.android.ui is on the SD card and not on internal storage)
Current behavior : partial sync on the SD card then "Offline syncing has stopped as there's no space left on this device" error message displayed but still 10+Gb available on SD card.
What I've tried : wipe app data / uninstall + full reinstall app
Thanks for your help :)
FIrst of all, thanks a lot for this preview and glad to see a new Android version of the Spotify app. The previous one was getting quite old now. The revamped UI is really cool and clean. However, I have some comments to make for improvements : No widget on this version either compatible with Android <3.x and/or compatible with Honeycomb/ICS with scrolling feature No landscape mode And more than that, no tablet optimized UI (!!). Come on, Android 4 aims to be used on both smartphones and tablets! No complete library screen to be able to shuffle among all the tracks added in all playlists No artist/album or library navigation while on offline mode No playback of local file anymore No crossface option But definitely a major improvement compared to the previous version. Nice work!!
A webapp version of Spotify would be great even if the webapp version doesn't support all the features of the desktop client. This would be useful when you want to use your Spotify on someone else's computer without the need of installing an standalone application. Alternatively, you could develop a Native Client for Chrome that would run directly inside the browser.