Deletion of domains generating problems with Spotify App #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3 issue related to some domains that caused multiple anomalies in the Spotify app for Google Pixel 4a / Android 13.
About
The first domain to be removed was
edge-web.dual-gslb.spotify.com
, which was redirected via a CNAME entry in the DNS domainlogin5.spotify.com
, and which apparently handled the user authentication process.The ````mobile-ap.spotify.com``` domain, which was responsible for checking if the app was connected to Spotify's servers, and therefore blocking it caused an anomaly in the application, is also removed.
Finally the Google Pixel 4a device was added to the Testing section of the README as a working device, after verifying that the app was now working correctly.
Thanks to @mfjt for the report.