Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Repeated crash while loading timeline after login – iOS 16.5 / X 12.31.1 / Tool 7.1.1

Open
#128 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ios, objective-c

Research direction

The crash log points to cacheAccountPair in BHTwitter.dylib, reached through storeWebCookies, harvestSharedCookies and webRequestFromNativeSend from the hooked NSURLSession dataTaskWithRequest. Start by reading how cacheAccountPair writes to NSUserDefaults with setObject:forKey: and what the cookie values look like at that point. Done means the app reopens after web login without the roughly 20-second hang and crash, which needs a device or simulator with a logged-in account.

Written by the indexing model from the issue text.

Description

bug

Describe the bug

The app repeatedly crashes after logging in while attempting to load tweets.

On the first launch, the app opens normally and allows me to log in using X (Twitter) Web authentication. After logging in, the app crashes, which is expected according to the developer’s instructions.

However, when I reopen the app, it stays on the loading screen while trying to load tweets for approximately 20 seconds before crashing again.

This happens every time I reopen the app, making it completely unusable.

I also tried completely clearing the app’s data using App Admin, but the issue still persists.

To Reproduce

Steps to reproduce the behavior:
1. Open the app.
2. Log in to your X (Twitter) account using Web authentication.
3. The app crashes after login (expected behavior according to the developer).
4. Reopen the app.
5. The app attempts to load the timeline.
6. After approximately 20 seconds, the app crashes.
7. Reopening the app results in the same crash repeatedly.

Expected behavior

After the initial expected crash following login, the app should reopen normally, load the timeline, and allow me to use it without crashing.

Screenshots

N/A

Please fill out the following info:
• Device: iPhone 14 Pro Max
• OS: iOS 16.5
• Developer Tool Version: 7.1.1
• X (Twitter) Version: 12.31.1

Additional context
• The initial crash immediately after X Web authentication is expected according to the developer’s instructions.
• The actual issue is the repeated crash approximately 20 seconds after reopening the app while the timeline is loading.
• I completely cleared the app’s data using App Admin and tried again, but the issue persists.
• The app never successfully loads the timeline.
• The issue occurs consistently on every launch after login

Crash Log Analysis

I managed to capture a crash log that may help identify the issue.

Crash details:
• Date: October 11, 2026
• Device: iPhone 14 Pro Max
• iOS: 16.5
• X (Twitter) Version: 12.31.1
• Developer Tool Version: 7.1.1
• Exception: EXC_BAD_ACCESS (SIGSEGV)
• Exception Subtype: KERN_INVALID_ADDRESS
• Reported Culprit: BHTwitter.dylib
• Crashed Thread: 35

Relevant stack trace:

18 Foundation -[NSUserDefaults setObject:forKey:]
19 BHTwitter.dylib cacheAccountPair
20 BHTwitter.dylib storeWebCookies
21 BHTwitter.dylib harvestSharedCookies
22 BHTwitter.dylib webRequestFromNativeSend
23 BHTwitter.dylib _logos_method$_ungrouped$NSURLSession$dataTaskWithRequest$

The crash appears to occur while BHTwitter.dylib is processing web authentication cookies and attempting to cache account-related data using NSUserDefaults.

This might indicate an issue with cookie handling, account caching, or preference serialization.

The crash happens consistently approximately 20 seconds after reopening the app following X Web authentication.

I have already tried completely clearing the app’s data using App Admin, but the issue persists

Dominant language
Objective-C
Stars
1.7k
Forks
133
Avg merge
11h 3m
Merged PRs (30d)
10

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoFreeBird/app

All issues in NeoFreeBird/app

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.