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
The mobile app page (e.g. https://events.opensuse.org/conferences/oSLO/schedule/app) contains a link to a xml schedule that can be imported to giggity. It also has a QR code that I assumed would point to the same xml, so that I can scan that qr via my cell phone from giggity. Unfortunately, it points to the html schedule and I have to enter the schedule url manually.
Expected correct behavior:
(Imho) The QR code should point to the xml schedule, so that it can be scanned from withing giggity (it has an option to explicitly do that)
Steps to reproduce:
Go to the schedule of a conference, click on Get the mobile app!, try to scan the QR in giggity and get a failure because it expects an XML schedule and not a html page.
Other information:
My request might have been the previous behavior, which was reverted by @hennevogel in e6049ad, but my Ruby knowledge is insufficient to be sure here.
The text was updated successfully, but these errors were encountered:
I'm submitting a ..
Current behavior:
The mobile app page (e.g. https://events.opensuse.org/conferences/oSLO/schedule/app) contains a link to a xml schedule that can be imported to giggity. It also has a QR code that I assumed would point to the same xml, so that I can scan that qr via my cell phone from giggity. Unfortunately, it points to the html schedule and I have to enter the schedule url manually.
Expected correct behavior:
(Imho) The QR code should point to the xml schedule, so that it can be scanned from withing giggity (it has an option to explicitly do that)
Steps to reproduce:
Go to the schedule of a conference, click on
Get the mobile app!
, try to scan the QR in giggity and get a failure because it expects an XML schedule and not a html page.Other information:
My request might have been the previous behavior, which was reverted by @hennevogel in e6049ad, but my Ruby knowledge is insufficient to be sure here.
The text was updated successfully, but these errors were encountered: