You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reporting a bug in the Onion OS (Note that Onion devs can’t fix inherited issues with RA Cores)
I have reviewed the Onion Wiki and did not find the answer
I have searched the existing (open and closed) issues to ensure I do not log a duplicate
Onions OS Version
v4.2.0-beta-dev-96c87c3
Miyoo Firmware Version
202305052130
Provide a clear and concise description of the issue
Received the "Fail to connect Check your password or reboot router" error when attempting to connect to a WIFI access point that contains a "#" character in the SSID.
Note - to be clear this is for special characters in the SSID, not the password as has been previously reported.
Steps to Reproduce
Turn on WIFI --> select SSID with a # in the name --> enter password --> "Fail to connect Check your password or reboot router" error received.
Provide any additional context or information that may help us investigate your issue
After creating a new SSID without the "#", it connects as expected.
The text was updated successfully, but these errors were encountered:
Checklist
Onions OS Version
v4.2.0-beta-dev-96c87c3
Miyoo Firmware Version
202305052130
Provide a clear and concise description of the issue
Received the "Fail to connect Check your password or reboot router" error when attempting to connect to a WIFI access point that contains a "#" character in the SSID.
Note - to be clear this is for special characters in the SSID, not the password as has been previously reported.
Steps to Reproduce
Turn on WIFI --> select SSID with a # in the name --> enter password --> "Fail to connect Check your password or reboot router" error received.
Provide any additional context or information that may help us investigate your issue
After creating a new SSID without the "#", it connects as expected.
The text was updated successfully, but these errors were encountered: