[GH-ISSUE #2014] View Size Behind Notification bar #1346

Closed
opened 2026-02-25 22:39:45 +03:00 by kerem · 16 comments
Owner

Originally created by @Bikholf on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2014

Which version of floccus are you using?

5.5.6

How many bookmarks do you have, roughly?

100

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Samsung Galaxy S24+ Android 15

Which version of Nextcloud Bookmarks are you using? (if relevant)

15.1.3

Which version of Nextcloud? (if relevant)

NC AIO 14.4.0

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

When starting the android app half of the app's header appears behind the phones status bar. So I am only able to reach the lower half of the buttons in the header.

Image
Image

floccus-5.5.6-2025-08-01-redacted.log

Expected Behavior

The header should appear beneath the status bar so you are able to full reach the buttons.

To Reproduce

Just start the android app.

Debug log provided

  • I have provided a debug log file
Originally created by @Bikholf on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2014 ### Which version of floccus are you using? 5.5.6 ### How many bookmarks do you have, roughly? 100 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Samsung Galaxy S24+ Android 15 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 15.1.3 ### Which version of Nextcloud? (if relevant) NC AIO 14.4.0 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug When starting the android app half of the app's header appears behind the phones status bar. So I am only able to reach the lower half of the buttons in the header. ![Image](https://github.com/user-attachments/assets/62e51468-637b-4bbf-82c0-7adf63927225) ![Image](https://github.com/user-attachments/assets/7579847d-f8a3-4be9-8806-8b4301101593) [floccus-5.5.6-2025-08-01-redacted.log](https://github.com/user-attachments/files/21555592/floccus-5.5.6-2025-08-01-redacted.log) ### Expected Behavior The header should appear beneath the status bar so you are able to full reach the buttons. ### To Reproduce Just start the android app. ### Debug log provided - [x] I have provided a debug log file
kerem 2026-02-25 22:39:45 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Aug 1, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

<!-- gh-comment-id:3146014399 --> @github-actions[bot] commented on GitHub (Aug 1, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Aug 2, 2025):

Thank you @Bikholf for taking the time to give feedback. I have not been able to consistently reproduce this. For me this only happens when I open floccus in certain circumstances that escape me at the moment, but the traditional

  1. Go to home screen
  2. Tap on floccus icon

Does not reproduce this for me :/

<!-- gh-comment-id:3146299118 --> @marcelklehr commented on GitHub (Aug 2, 2025): Thank you @Bikholf for taking the time to give feedback. I have not been able to consistently reproduce this. For me this only happens when I open floccus in certain circumstances that escape me at the moment, but the traditional 1. Go to home screen 2. Tap on floccus icon Does not reproduce this for me :/
Author
Owner

@marcelklehr commented on GitHub (Aug 2, 2025):

I've relayed this to the folks from capacitor, the mobile framework used by floccus.

<!-- gh-comment-id:3146300864 --> @marcelklehr commented on GitHub (Aug 2, 2025): I've relayed this to the folks from capacitor, the mobile framework used by floccus.
Author
Owner

@heapifyman commented on GitHub (Aug 5, 2025):

I am experiencing the same issue with floccus 5.5.6 on a Google Pixel 6 with GrapheneOS (Android 16). Even when doing

  1. Go to home screen
  2. Tap on floccus icon

Basically, floccus is unusable right now. I cannot search for bookmarks, or trigger a sync, or open the settings. All those UI elements are blocked by the phone's status bar. Creating new bookmarks via share dialog is also not possible. I cannot click the Save button because it's blocked by the phone's status bar.

Is there any recommended workaround until this gets fixed in capacitor?

<!-- gh-comment-id:3154997315 --> @heapifyman commented on GitHub (Aug 5, 2025): I am experiencing the same issue with floccus 5.5.6 on a Google Pixel 6 with GrapheneOS (Android 16). Even when doing > 1. Go to home screen > 2. Tap on floccus icon Basically, floccus is unusable right now. I cannot search for bookmarks, or trigger a sync, or open the settings. All those UI elements are blocked by the phone's status bar. Creating new bookmarks via share dialog is also not possible. I cannot click the Save button because it's blocked by the phone's status bar. Is there any recommended workaround until this gets fixed in capacitor?
Author
Owner

@marcelklehr commented on GitHub (Aug 5, 2025):

@heapifyman Mmh, can you try v5.6.0? It will be live on Google Play soon. I don't have this on a Pixel 6a with latest Graphene OS with floccus v5.6.0 🤔

<!-- gh-comment-id:3155566078 --> @marcelklehr commented on GitHub (Aug 5, 2025): @heapifyman Mmh, can you try [v5.6.0](https://github.com/floccusaddon/floccus/releases/download/v5.6.0/floccus-build-v5.6.0.apk)? It will be live on Google Play soon. I don't have this on a Pixel 6a with latest Graphene OS with floccus v5.6.0 🤔
Author
Owner

@marcelklehr commented on GitHub (Aug 5, 2025):

Is there any recommended workaround until this gets fixed in capacitor?

I don't think there is. I'm looking into this soon, apparently many people are affected by this...

<!-- gh-comment-id:3155627896 --> @marcelklehr commented on GitHub (Aug 5, 2025): > Is there any recommended workaround until this gets fixed in capacitor? I don't think there is. I'm looking into this soon, apparently many people are affected by this...
Author
Owner

@heapifyman commented on GitHub (Aug 5, 2025):

@heapifyman Mmh, can you try v5.6.0? It will be live on Google Play soon. I don't have this on a Pixel 6a with latest Graphene OS with floccus v5.6.0 🤔

I tried v5.6.0 but that did not change anything.

BTW, I installed floccus from f-droid - don't have any google stuff on that phone. Not sure if that is relevant

<!-- gh-comment-id:3155742633 --> @heapifyman commented on GitHub (Aug 5, 2025): > [@heapifyman](https://github.com/heapifyman) Mmh, can you try [v5.6.0](https://github.com/floccusaddon/floccus/releases/download/v5.6.0/floccus-build-v5.6.0.apk)? It will be live on Google Play soon. I don't have this on a Pixel 6a with latest Graphene OS with floccus v5.6.0 🤔 I tried `v5.6.0` but that did not change anything. BTW, I installed floccus from f-droid - don't have any google stuff on that phone. Not sure if that is relevant
Author
Owner

@marcelklehr commented on GitHub (Aug 5, 2025):

Alright, I'll try to fix this as soon as possible!

<!-- gh-comment-id:3155764079 --> @marcelklehr commented on GitHub (Aug 5, 2025): Alright, I'll try to fix this as soon as possible!
Author
Owner

@heapifyman commented on GitHub (Aug 5, 2025):

I tried this approach of setting adjustMarginsForEdgeToEdge, and also updated all capacitor deps to their latest version.

That seemed to have helped. See patch.tar.gz

<!-- gh-comment-id:3155902065 --> @heapifyman commented on GitHub (Aug 5, 2025): I tried [this approach of setting `adjustMarginsForEdgeToEdge`](https://github.com/ionic-team/capacitor/issues/8093#issuecomment-3153853282), and also updated all capacitor deps to their latest version. That seemed to have helped. See [patch.tar.gz](https://github.com/user-attachments/files/21604011/patch.tar.gz)
Author
Owner

@Bikholf commented on GitHub (Aug 5, 2025):

I can confirm it. For me this solution worked. Just adding

{
  "plugins": {
    "EdgeToEdge": {
      "backgroundColor": "#ffffff"
    }
  }
}

to the capacitor.config.json file

Image
Image

<!-- gh-comment-id:3156150690 --> @Bikholf commented on GitHub (Aug 5, 2025): I can confirm it. For me this solution worked. Just adding ``` { "plugins": { "EdgeToEdge": { "backgroundColor": "#ffffff" } } } ``` to the `capacitor.config.json` file ![Image](https://github.com/user-attachments/assets/52e383a2-5717-4199-b35b-20d324064bd0) ![Image](https://github.com/user-attachments/assets/f6903a3d-60a3-4d9b-aca7-adcca1874c08)
Author
Owner

@oloukanov commented on GitHub (Aug 9, 2025):

Same issue here.

Floccus 5.6.0 - installed from Releases (with Obtainium)
Pixel 6a - navigation mode: Gesture navigation
Graphene OS - 2025080600

Temp workaround - turn phone to landscape mode to be able to access the top buttons.

<!-- gh-comment-id:3169619233 --> @oloukanov commented on GitHub (Aug 9, 2025): Same issue here. Floccus 5.6.0 - installed from Releases (with Obtainium) Pixel 6a - navigation mode: Gesture navigation Graphene OS - 2025080600 Temp workaround - turn phone to landscape mode to be able to access the top buttons.
Author
Owner

@andbenn commented on GitHub (Aug 16, 2025):

Pixel 9a on the August edition. I just got Floccus 5.6.0 in the Play Store and am seeing this now in Floccus.

Aart Bik's Chess and Reversi games demonstrate this as well. He added an option called "Full Screen" which hides the system notification bar, allowing one to use the top part of the app that was formerly obscured by the notification/status bar.

Also as recommended, go landscape instead of portrait.

<!-- gh-comment-id:3193973036 --> @andbenn commented on GitHub (Aug 16, 2025): Pixel 9a on the August edition. I just got Floccus 5.6.0 in the Play Store and am seeing this now in Floccus. Aart Bik's Chess and Reversi games demonstrate this as well. He added an option called "Full Screen" which hides the system notification bar, allowing one to use the top part of the app that was formerly obscured by the notification/status bar. Also as recommended, go landscape instead of portrait.
Author
Owner

@andbenn commented on GitHub (Aug 19, 2025):

This problem is still vexing other app devs. Inoreader (the RSS reader app/service) in 7.9.3 fixed a similar issue with their Discover search feature, where their menu was obscured by the time in the status bar.

<!-- gh-comment-id:3198815434 --> @andbenn commented on GitHub (Aug 19, 2025): This problem is still vexing other app devs. Inoreader (the RSS reader app/service) in 7.9.3 fixed a similar issue with their Discover search feature, where their menu was obscured by the time in the status bar.
Author
Owner

@jordan-bravo commented on GitHub (Aug 20, 2025):

I am also having this problem on a Pixel 9 running the latest version of GrapheneOS.

Floccus version is 5.6.0 installed from GitHub releases using Obtainium.

<!-- gh-comment-id:3203615769 --> @jordan-bravo commented on GitHub (Aug 20, 2025): I am also having this problem on a Pixel 9 running the latest version of GrapheneOS. Floccus version is `5.6.0` installed from GitHub releases using Obtainium.
Author
Owner

@marcelklehr commented on GitHub (Aug 20, 2025):

The above fix will be in the next release. Thank you for weighing in and giving feedback! I'm still fighting with another status bar issue, where the text color is not adjusted to the background color for some reason :/

<!-- gh-comment-id:3205401903 --> @marcelklehr commented on GitHub (Aug 20, 2025): The above fix will be in the next release. Thank you for weighing in and giving feedback! I'm still fighting with another status bar issue, where the text color is not adjusted to the background color for some reason :/
Author
Owner

@marcelklehr commented on GitHub (Aug 27, 2025):

This should be fixed now in v5.7.0

<!-- gh-comment-id:3228448831 --> @marcelklehr commented on GitHub (Aug 27, 2025): This should be fixed now in v5.7.0
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#1346
No description provided.