element-hq / element-hq/element-ios
Location sharing: Authorize only one beacon info per room and per member in the SDK
- Dominant language
- Swift
- Stars
- 1.8k
- Forks
- 544
- PR merge metrics
- PR metrics pending
Description
In the SDK you can see that starting multiple time live location sharing creates multiple `MXBeaconInfoSummary` for the current user in the `MXBeaconInfoSummaryMemoryStore` with live status.
- We should stop other beacon info before starting a new one in a room.
- We should only handle one beacon info per room for other users.
Contributor guide
Research direction
Start by locating MXBeaconInfoSummary and MXBeaconInfoSummaryMemoryStore in the SDK, then trace how live location sharing is started and how summaries are stored. Reproduce multiple live shares for the current user and multiple members in one room. Done means only one active beacon info remains per room for the sharing user and for each other member.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100