Tickets and wallets A resident says only one ticket showed up in their wallet That was the old behaviour and it is fixed. An order now produces one pass per ticket. If they saved the order before...
Last updated
That was the old behaviour and it is fixed. An order now produces one pass per ticket. If they saved the order before this release, ask them to open their ticket link again and add it now.
One of the four was cancelled, and a cancelled ticket cannot become a pass. The panel says so before they choose, naming both numbers, so they are told rather than left to count.
They save just that ticket, then share the pass from their wallet. Each ticket carries its own code, so the shared one works on its own and theirs still works.
Almost always they are on a laptop. A wallet pass has to be added on the phone that will carry it. Ask them to open the ticket link on their phone.
The event has no photo on it. The pass falls back to the standard dark design. Add a photo to the event and future passes pick it up.
No. The link in their ticket email opens the ticket page in any phone browser, and the wallet buttons are there. This matters for guests who are not residents of your building.
A code on one of your own news items opens that article in the resident portal. A code on one of your own events opens that event's page, which works for someone who is not signed in. Codes on curated or neighbourhood content keep opening the publisher's own page.
Before this release these codes pointed at an address that does not exist, so scanning one led nowhere. Codes already printed and hanging on screens were repaired, not just newly generated ones.
That is the old dead link, from a code generated before this release. It has been repaired centrally, so rescanning the same code now works. Nothing needs reprinting.
That is intended. The portal opens for everyone, whether or not they have the app installed, and hands people who do have it through to the app. Pointing a printed code straight at the app would throw an error at every person who does not have it, which is the failure this replaced.
Check that Displays is enabled for the property in Property Settings. If it is off, neither events nor news appear.
Events clear about two hours after they end. If you cancelled rather than ended one, unpublish it and it leaves the rotation.
Fixed. Emptying the description field and saving now saves normally. Previously the entire save was rejected, so any other change made at the same time was lost too, with no error shown.
Fixed. Scheduling now records who scheduled it at the moment you schedule. Previously, on an event with no recorded creator, the announcement could never be built and would sit waiting indefinitely while the screen said it was scheduled. Reschedule any announcement you are still waiting on.