[GH-ISSUE #1523] Text Editor in Proxyman displays garbage (Nothing but question marks) #1515

New issue

Open

opened 2026-03-03 19:52:06 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:52:06 +03:00

Owner

Originally created by @Mark-Frick-Thrivent on GitHub (Feb 3, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1523

Description

Text Editor displays garbage. Problem with font?

Steps to Reproduce

1.) Start Android emulator
2.) Open Proxyman 4.1.0, Certificate > Install on Android > Emulator... Garbage displays in text editor
3.) Override Emulator
4.) Generate Network Traffic
5.) Select "Body" in Request and Response window... Garbage displays in Request and Response window

Current Behavior

Garbage displays, all question marks

Expected Behavior

Text should display normally

Environment

App version: e.g Proxyman 4.1.0 (41000)
macOS version: e.g macOS Ventura 13.1 (Chip: Apple M1 Pro)

Originally created by @Mark-Frick-Thrivent on GitHub (Feb 3, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1523 ## Description Text Editor displays garbage. Problem with font? ## Steps to Reproduce 1.) Start Android emulator 2.) Open Proxyman 4.1.0, Certificate > Install on Android > Emulator... Garbage displays in text editor 3.) Override Emulator 4.) Generate Network Traffic 5.) Select "Body" in Request and Response window... Garbage displays in Request and Response window  <img width="768" alt="image" src="https://user-images.githubusercontent.com/89422368/216678326-311908ed-fd42-4c8d-a60c-0aa78b34e053.png"> <img width="1736" alt="image" src="https://user-images.githubusercontent.com/89422368/216679525-1652401c-48d6-4bfd-adeb-f8f98173b53c.png"> ## Current Behavior Garbage displays, all question marks ## Expected Behavior Text should display normally ## Environment - App version: e.g Proxyman 4.1.0 (41000) - macOS version: e.g macOS Ventura 13.1 (Chip: Apple M1 Pro)

kerem added the

bug

label

2026-03-03 19:52:06 +03:00

kerem commented

2026-03-03 19:52:07 +03:00

Author

Owner

@Mark-Frick-Thrivent commented on GitHub (Feb 3, 2023):

Killing fontd and fontworker processes, then restarting the app corrected the issue

@Mark-Frick-Thrivent commented on GitHub (Feb 3, 2023): Killing `fontd` and `fontworker` processes, then restarting the app corrected the issue

kerem commented

2026-03-03 19:52:07 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 4, 2023):

It's odd. It's the first time I've encountered this issue @Mark-Frick-Thrivent

Do if happen again or it's already fixed?

@NghiaTranUIT commented on GitHub (Feb 4, 2023): It's odd. It's the first time I've encountered this issue @Mark-Frick-Thrivent Do if happen again or it's already fixed?

kerem commented

2026-03-03 19:52:07 +03:00

Author

Owner

@Mark-Frick-Thrivent commented on GitHub (Feb 6, 2023):

Haven't seen it since, but killing those two processes is a good enough work around for now. If it keeps coming up, I'll post more info.

@Mark-Frick-Thrivent commented on GitHub (Feb 6, 2023): Haven't seen it since, but killing those two processes is a good enough work around for now. If it keeps coming up, I'll post more info.