Skip to content
This repository has been archived by the owner on May 18, 2024. It is now read-only.

[Bug]: Apple Music login fails / shows beta webview ui #1770

Closed
4 tasks done
joelmgallant opened this issue Sep 17, 2023 · 4 comments
Closed
4 tasks done

[Bug]: Apple Music login fails / shows beta webview ui #1770

joelmgallant opened this issue Sep 17, 2023 · 4 comments
Labels
bug Something isn't working needs-triage Awaiting triage. stale Issues that are no longer active.

Comments

@joelmgallant
Copy link

Preflight Checklist

Cider Version

2.2.0

What operating system are you using?

macOS

Operating System Version

Sonoma 14.0 Beta (23A5337a)

Where did you download Cider from?

GitHub

Describe the Bug

Attempting to "Sign in with Apple Music" during first-time user experience.
Entered credentials, received 2FA notification, entered 2FA code.
Received the "trust this browser" message with a somewhat bizarre upper-left element:
SCR-20230917-khou
Trusted, instead being redirected to
SCR-20230917-khqe
a semi-authenticated beta web ui?

Steps to Reproduce

(documented in description)

  • fresh install from .DMB
  • new "Sign in with Apple Music" user
  • attemped also to Skip / Bypass login and try after FTUE -- same result

Anything else?

Logs from running with terminal (sensitive strings > xxxxxx)

2023-09-17 11:17:59.261 Cider[79624:3043036] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
App is ready
Loading module: com.ciderapp.menubar
Menubar Loaded
Loading module: com.ciderapp.traymodule
Tray Loaded
Loading module: com.ciderapp.ciderrpc
[Electron:Modules][module:com.ciderapp.ciderrpc] CiderRPC Loaded
[Cider][Widevine] Status: {
  oimompecagnajdejgnnjijobebaeigek: {
    name: 'Widevine Content Decryption Module',
    status: 'new',
    version: '4.10.2652.2'
  }
}
(node:79624) electron: NSVisualEffectMaterialDark has been deprecated and removed as of macOS 10.15.
(Use `Cider --trace-warnings ...` to show where the warning was created)
(node:79624) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/sandbox_bundle:2:55792
    at EventEmitter.<anonymous> (node:electron/js2c/sandbox_bundle:2:49921)
    at EventEmitter.emit (node:electron/js2c/sandbox_bundle:2:35718)
    at Object.onMessage (node:electron/js2c/sandbox_bundle:2:47988)
(node:79624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:79624) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/sandbox_bundle:2:55792
    at EventEmitter.<anonymous> (node:electron/js2c/sandbox_bundle:2:49921)
    at EventEmitter.emit (node:electron/js2c/sandbox_bundle:2:35718)
    at Object.onMessage (node:electron/js2c/sandbox_bundle:2:47988)
(node:79624) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:79624) electron: Failed to load URL: https://idmsa.apple.com/appleauth/auth/authorize/signin?frame_id=auth-xxxxxxxx&language=en_us&skVersion=7&iframeId=auth-xxxxxxxxxl&client_id=xxxxxxxx&redirect_uri=https://music.apple.com&response_type=code&response_mode=web_message&account_ind=1&state=auth-xxxxxxx&authVersion=latest with error: ERR_BLOCKED_BY_RESPONSE
App is quitting

Attempting to quit app also requires force-quit due to message:
SCR-20230917-kijc

@joelmgallant joelmgallant added bug Something isn't working needs-triage Awaiting triage. labels Sep 17, 2023
@github-actions
Copy link

Support for Cider 1.0 is in a reduced state. Do not expect replies or acknowledgement for issues that do not break full functionality of the app (Media playback, plugin functionality etc.).

If you are interested in joining the Cider 2 open alpha, you can join our Discord here.

@github-project-automation github-project-automation bot moved this to Backlog 📖 in Cider - Bug Reports Sep 17, 2023
@manuel2258
Copy link

I also have to exact same issue.
My system:

~ @ uname -a
Linux archlinux 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 unknown unknown linux

Looking at the console output I see a similar output:

~ @ cider
App is ready
Loading module: com.ciderapp.menubar
Menubar Loaded
Loading module: com.ciderapp.traymodule
Tray Loaded
Loading module: com.ciderapp.ciderrpc
[Electron:Modules][module:com.ciderapp.ciderrpc] CiderRPC Loaded
[Cider][Widevine] Status: {
  oimompecagnajdejgnnjijobebaeigek: {
    name: 'Widevine Content Decryption Module',
    status: 'new',
    version: '4.10.2652.2'
  }
}
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
(node:38950) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/sandbox_bundle:2:55792
    at EventEmitter.<anonymous> (node:electron/js2c/sandbox_bundle:2:49921)
    at EventEmitter.emit (node:electron/js2c/sandbox_bundle:2:35718)
    at Object.onMessage (node:electron/js2c/sandbox_bundle:2:47988)
(Use `cider --trace-warnings ...` to show where the warning was created)
(node:38950) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:38950) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/sandbox_bundle:2:55792
    at EventEmitter.<anonymous> (node:electron/js2c/sandbox_bundle:2:49921)
    at EventEmitter.emit (node:electron/js2c/sandbox_bundle:2:35718)
    at Object.onMessage (node:electron/js2c/sandbox_bundle:2:47988)
(node:38950) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Interesting is that the first time when I press the 'Sign into Apple Music' button nothing happens, and then when I press it the second time the sign in window appears as well and the error with (rejection id: 1) is logged. @joelmgallant can you confirm the same behavior?

Also maybe something interesting to add, after I press the 'Trust this browser' button, I get a prompt to change my location. And then when I click the 'Continue' button the error with (rejection id: 2) is logged.
image

@joelmgallant
Copy link
Author

Interesting is that the first time when I press the 'Sign into Apple Music' button nothing happens, and then when I press it the second time the sign in window appears as well and the error with (rejection id: 1) is logged. @joelmgallant can you confirm the same behavior?

100% agreed -- I missed that detail 🙇

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issues that are no longer active. label Oct 19, 2023
@github-project-automation github-project-automation bot moved this from Backlog 📖 to Completed / Merged into Main 🚀 in Cider - Bug Reports Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working needs-triage Awaiting triage. stale Issues that are no longer active.
Projects
Status: Completed 🚀
Development

No branches or pull requests

2 participants