When adding custom components as buttons on topBar->rightButtons, it causes the topBar to glitch and collapse the title.
Both topBar and rightButtons were custom components. It did not appear to collapse when using a standard text component as the title.
topBar-->rightButtons (components)
topBar-->title (component)
@retyui
Nah that's not it.
Here's what you should try, attempt to create a custom component for your right button, and a custom component for your title.
options: {
topBar: {
title: {
component: {} // Insert a custom title component here, obviously register it first and use the appropriate component name e.g. <View><Text>Title</Text></View>
},
rightButtons: [
{
id: '1',
component: {} // Apply a marginRight to the component's root <View>
},
],
}
}
I update the example https://gist.github.com/retyui/16a275c8cb3c322dab4dd858515d457f
And here is the result:

I get the same behavior. RNN 2.8.0, RN 57.4 , Android Sim.
@retyui yep, that's exactly what happens. iOS is completely fine. My solution was just to add
paddingRight: 10
instead of marginRight
@harveyconnor Did paddingRight exhibit strange behaviour for you?
I distinctly remember adding this attribute and what happened was that the element I had slid left and bumped up against the title...
kind of like a skater going across the ice, a nice effect but not what I was _really_ after. :wink:
@juddey This is what I have:
container: {
...Platform.select({
android: {
paddingRight: 16,
marginLeft : 8,
},
}),
},
On iOS the marginRight is in there natively
Hmmm.
Variation on your problem then:

yeah that was the original issue I had
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.
This is still an issue (2.17)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.
No no no no no stalebot, this is still a problem. :robot:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.
The issue has been closed for inactivity.
Still existing on 3.0.0
Most helpful comment
This is still an issue (2.17)