<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SongShift on Medium]]></title>
        <description><![CDATA[Stories by SongShift on Medium]]></description>
        <link>https://medium.com/@SongShift?source=rss-d0927bef2a07------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yXq2IEt09pNWGDQw.jpg</url>
            <title>Stories by SongShift on Medium</title>
            <link>https://medium.com/@SongShift?source=rss-d0927bef2a07------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:54:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SongShift/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[So, what’s with the “Sign In to iTunes Store” alert and SongShift?]]></title>
            <link>https://medium.com/@SongShift/so-whats-with-the-sign-in-to-itunes-store-alert-and-songshift-3f141d74669b?source=rss-d0927bef2a07------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f141d74669b</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[broken]]></category>
            <category><![CDATA[apple-music]]></category>
            <dc:creator><![CDATA[SongShift]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 15:05:06 GMT</pubDate>
            <atom:updated>2018-06-18T15:05:06.242Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone, I wanted to take a second and talk about something I’ve received many support emails about — the dreaded “Sign In to iTunes Store” alert. Today, a new update is rolling out which makes the purpose of this alert much more important than ever. Due to this, I wanted to clear up what it does and why SongShift causes the alert to appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0j-irLAgmPXXzzgGncmVw.png" /></figure><p>With the introduction of MusicKit in iOS 11, Apple added new API’s to interact with Apple Music. Interacting with these new API’s requires a developer token — to authenticate the developer accessing the API, and a music user token — to authenticate access to the user music library.</p><p>The “Sign In to iTunes Store” alert appears when SongShift requests a music user token. This token authenticates that you gave persmission for SongShift to access and modify your Apple Music library. I understand the alert is vague and doesn’t display anything to indicate it’s requesting a user token or related to SongShift in any way. I wish I could fix this since it’s aggravating to users but there’s nothing I can do :/ What makes it worse is, as with most access tokens, Apple Music user tokens expire and need to be renewed. When this happens, the alert appears once again.</p><p>So now that we know the cause of it, what can we do? <strong>Nothing</strong></p><p>This alert will continue to appear and it’s important to enter your password for SongShift to be able to get a new user token. Without it, the app literally cannot transfer songs to Apple Music.</p><p>With the latest update, 3.1.10, I’ve added an alert which appears before requesting a user token. This at least lets users know what is about to happen. It’s not the best solution, worse even since it adds a second alert, but it’s a step up from not knowing what the alert means.</p><p><strong>There’s got to be a better solution right?</strong></p><p>I thought so too and to this day I still believe this is a bug. I submitted a bug report to Apple as soon as iOS 11 beta 1. (#32713483 submitted June 12th 2017). In this report I explained how it seemed redundant to ask the user to enter their password in a vague alert when they’ve already given access to the app via the media libary permission dialog. Nothing ever came of this bug report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjHqP5pttdZTGY2pAqPIBw.png" /></figure><p>I again submitted a bug report May 30th 2018 (#40652411, which got marked as duplicate of #40725283, hmm). In this bug report I explained how the user token expires way too quickly — typically a little over 24 hours. I went on to explain how the token expiring this quickly is causing a really bad user experience for my app due to an active token being needed constantly. Other than it being marked a duplicate of a later bug report, I have not heard back about this issue.</p><p><strong>In Closing</strong></p><p>I’m sorry I don’t have better news about this issue right now. I truly believe interrupting the user with this alert is unacceptable. I’m not sure how anybody working on these API’s thought this was a good idea or why they continue to let it happen.</p><p>Thank you for bearing with us as we continue to work on making the experience with this alert better. The SongShift team (there’s now two of us 😃🎉) has been working on some awesome new things and we cannot wait to share them with you. There’s a lot more coming this year to SongShift and more.</p><p>— Carlos</p><p>p.s</p><p>Please don’t send disparaging support emails because of alert. They really don’t help and only make me feel worse about a situation I have no control over :(</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f141d74669b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>