Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bottom Navigation Bar Icons Not Displaying in Seafile Pro iOS App on iOS 18.1 (22B5007p, beta) #381

Open
Rubatharisan opened this issue Aug 11, 2024 · 2 comments

Comments

@Rubatharisan
Copy link

Rubatharisan commented Aug 11, 2024

In the Seafile Pro iOS app running on iOS 18.1 (22B5007p, beta), the bottom navigation bar is not displaying icons correctly. The bar is still clickable, meaning the touch areas respond to user interaction, but the icons themselves are not visible. This issue is specific to the Seafile Pro app and persists throughout the app’s various screens.

Steps to Reproduce:

1.	Install iOS 18.1 (22B5007p, beta) on an iPhone device.
2.	Open the Seafile Pro iOS app.
3.	Observe the bottom navigation bar, where the icons should be displayed.

Expected Behavior:
The bottom navigation bar in the Seafile Pro app should display the appropriate icons for each navigation item (e.g., Libraries, Activity, Settings).

Actual Behavior:
The bottom navigation bar is visible and clickable, but the icons for the navigation items are not shown. The touch targets work, allowing navigation to different sections, but without visual feedback, it’s unclear what each section of the bar represents.

Environment:

•	Device: iPhone 15 Pro Max
•	OS Version: iOS 18.1 (22B5007p, beta)
•	App Version: Seafile Pro 2.9.26
•	iOS Build Number: 22B5007p

Additional Information:

•	The issue persists after restarting the device.
•	Toggling dark mode or adjusting accessibility settings does not resolve the issue.
•	The problem occurs specifically within the Seafile Pro app.
•	This issue does not appear in other apps on iOS 18.1.

Screenshots:
IMG_20240812_010854_1620

@lilthree
Copy link
Contributor

This is a known issue, and it will be fixed in the next version.

@Rubatharisan
Copy link
Author

Cool, thank you @lilthree .
Do you have an idea of when the next version will be released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants