lichess-org / lichobile

lichess.org mobile application
https://lichess.org/mobile
GNU General Public License v3.0
2.04k stars 318 forks source link

Unable to “Play with a Friend” #1468

Open groovyf opened 3 years ago

groovyf commented 3 years ago

Since the most recent iOS app update (5 days ago) I am unable to create games via the Play With A Friend option.

To Reproduce When tapping the Play With a Friend option, then selecting all required game options and tapping Play With A Friend button a message box appears stating “Anonymous is inviting you”, with text stating “Join” that cannot be tapped. Unable to tap on anything at all and the only option is to swipe up and forcibly exit the game.

Expected behavior The usual behaviour for choosing play with friend is to have a URL appear that can be shared with opponent.

Screenshots 202F544B-09E6-497F-849E-4BB9EDCE43E1

Smartphone (please complete the following information):

Additional context I have deleted and redone loaded the lichess app on my iPhone and iPad multiple times but still the same issue persists. Another member of the family has same problem on their iPad. Oddly, a newly purchased iPad Pro (brand new setup with iOS 14.3) has downloaded and installed lichess and this works OK. Could it be still some lichess data hanging around on the iPhone/iPad after being deleted from the device?

vineet131 commented 1 year ago

I wanted to add that I am facing this exact same issue. I'm on an Android 11 device, with the version 8.0.0 of the app. Would some maintainers please like to take a look at this issue?

Fogapod commented 1 year ago

Same behavior on android 13. Sometimes i manage to click somewhere around accept butter and it displays loading animation for a fraction of a second but nothing changes. No link in clipboard. This feature is broken entirely.

EDIT:

after logging into account i am able to create a game. either this button should be removed because anonymous players aren't allowed to create games or something is broken there

Zidras commented 1 year ago

Issue still persists on v8.0.0