-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: cider APP BETA does not connect to desktop queue as remote #569
Comments
Please expand on your issue and what version of the app you are using |
I do not see how I'm supposed to expand on a blank screen, the app essentially does not function in any way besides logging in to Apple Music. app version: testflight cider remote 2.1 (8) |
So are you on about the iOS remote app? |
I’m pretty sure that’s abundantly clear by now.On Mar 13, 2024, at 2:16 PM, Core ***@***.***> wrote:
So are you on about the iOS remote app?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
That still doesnt make it clear, you literally just replied a email footer. If you prefer I can not help you. You have just complained about the app beta being blank and not connecting to desktop queue, whatever that means. If this issue is related to the iOS app as you havent made clear at all. You havent said if this is an issue with the Remote app on iOS or the desktop app. From everything you've said, I'm just gonna go off you this being an issue with the iOS app, in which case, this app is not currently being supported, the main developer assigned to this has been focused on other areas. As only one developer has made and developed this, this is out of my control. If you really want this app to be working I suggest reaching out to Swiftzerr (the app dev). I cannot take this any further here. If I got it wrong and you're on about the desktop app, reply and I'll reopen the ticket. The next time you open a ticket, please follow the template carefully and actually state the steps to recreate, dont just skip through because you want to complain. |
This is just paragraphs of slop, what work do you think you’re accomplishing with this? Ask a pointed question off-bat instead of telling me it’s incomplete. I provided an obvious app version alongside iOS version which should have made it perfectly clear what I’m discussing. THE REMOTE APP IS BLANK: there is literally nothing else for me to provide. Up front, if you understood the product system it seems you would have quickly noted that this is no longer a function. Absurdly Idiotic really that I could sign up for a beta that is no longer functioning. Y’all gotta shut that down and pass on the memo so we don’t get our hopes up. I really expected more professionality here. This was childish to read and respond to. On Mar 14, 2024, at 1:46 PM, Core ***@***.***> wrote:
That still doesnt make it clear, you literally just replied a email footer. If you prefer I can not help you. You have just complained about the app beta being blank and not connecting to desktop queue, whatever that means. If this issue is related to the iOS app as you havent made clear at all. You havent said if this is an issue with the Remote app on iOS or the desktop app.
From everything you've said, I'm just gonna go off you this being an issue with the iOS app, in which case, this app is not currently being supported, the main developer assigned to this has been focused on other areas. As only one developer has made and developed this, this is out of my control. If you really want this app to be working I suggest reaching out to Swiftzerr (the app dev).
I cannot take this any further here. If I got it wrong and you're on about the desktop app, reply and I'll reopen the ticket.
The next time you open a ticket, please follow the template carefully and actually state the steps to recreate, dont just skip through because you want to complain.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
We are not paid for this, nor are any of the other devs handling issues, so take my response as only what you're getting. If something is not working in the main app, then I might be able to do something, outside this I cannot do anything. Swift is well aware of the state of the app. I am not responding any more to you if you are just going to complain. And at no point during the issue did you say 'The remote app is blank'. We get a lot of issues, varying in degree and area of our project, so you saying 'app is blank' can imply both desktop or mobile app. All the best. |
I wouldn’t pay anyone for your thinking either lmao this coulda been so simple On Mar 14, 2024, at 6:18 PM, Core ***@***.***> wrote:
We are not paid for this, nor are any of the other devs handling issues, so take my response as only what you're getting. If something is not working in the main app, then I might be able to do something, outside this I cannot do anything. Swift is well aware of the state of the app. I am not responding any more to you if you are just going to complain.
And at no point during the issue did you say 'The remote app is blank'. We get a lot of issues, varying in degree and area of our project, so you saying 'app is blank' can imply both desktop or mobile app.
All the best.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Preflight Checklist
What operating system are you using?
Windows
Build Details
2.8.24
Operating System Version
Windows 10
Describe the Bug
The app is just blank and shows nothing playing, not sure if i set something up incorrectly or if it wasnt adapted for c2
Steps to Reproduce
everytime.
Anything else?
No response
Connect Device ID
No response
Build timestamp
1710027778365
The text was updated successfully, but these errors were encountered: