Greenstand / Greenstand/treetracker-android

App crash on User Selection during Capture flow (intermittant)

Open
#1,258 6 comments 0 reactions 0 assignees View on GitHub
2.2.1 beta bug triage
Dominant language
Kotlin
Stars
101
Forks
116
PR merge metrics
No merged PRs in 30d

Description

### App Version / Build Number

2.2.1 Build 202

### Device

Samsung Galaxy Tab A8

### Android Version

Android 14

### Describe the bug

While attempting to start a new capture, the app prompts for a phone number. After identifying an existing user and selecting the profile, the app immediately shuts down (hard crash).

Reproducibility: Intermittent (Occurred 1 out of 2 attempts).

Note: On the first attempt, the app suffered a hard crash immediately after selecting the existing user profile. On the second attempt, the app successfully moved past this screen. This suggests a potential stability issue during the authentication hand-off.

However, after the successful capture, the app does not persist the session. Navigating to other menus prompts the Privacy Policy and Phone Number screens again.

@cynthiabondi

### To Reproduce

1. Go to 'Track
2. Tap on Plus sign
3. Check yes on Privacy Policy
4. Enter Phone Number on Prompt
5. Pop-up Prompt to click your profile
6. App Shuts Down

### Expected behavior

Expected when I click my profile that I am taken to the profile screen, or a screen to record a tree.

### Actual behavior

On the first attempt, the app hard crashed after clicking the profile prompt. On the second attempt, I was taken to my profile and allowed to take a photo of a tree which was successful.

### Frequency

Intermittent

### Severity

Blocker - App crashes or data loss

### Network Conditions

Wi-Fi

### Screenshots / Screen recordings

_No response_

### Logs

```shell

```

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the flow from Track: tap Plus, accept the Privacy Policy, enter a phone number, and select the existing profile. Inspect the capture-flow authentication hand-off and session persistence around the profile-selection step; no source files or logs are identified in the issue. Done means the intermittent crash is resolved and a successful capture keeps the session when navigating to other menus.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.