Extra spacing issue in Android

[lucasferreira]

Extra spacing issue in Android

[lucasferreira]

Hi @vikrantnegi

That's weird thing... are you using message or title attribute in your showMessage call?

Could you swap to see if it gets better? Ex: if you are using:

showMessage({
  title: "Simple message",
  type: "info",
 });

Change to:

showMessage({
  message: "Simple message",
  type: "info",
 });

And vice-versa.

[vikrantnegi]

Hi,

I'm using this

showMessage({
   message: error,
});

and when I try to use title I get a warning and no text gets rendered in the message.

Warning: Failed prop type: The prop `message.message` is marked as required in `DefaultFlash`, but its value is `undefined`.

Even I try to use the normal flash messages without floating there still seems to be the spacing issue.

[lucasferreira]

Ok @vikrantnegi

I've made a simple test with Expo, you could look here: https://snack.expo.io/Sygi5skDH

If you test using the on-line android device we can't detect any "extra" spacing:

So I guess that you are facing some "special issue" that's only happens in your setup. What version of Android are you using? Are you testing in device or just in emulator?

[vikrantnegi]

@lucasferreira Weird. I just made a fresh react-native CLI project.

Can you clone the below repo and try running it on the Android Emulator?

Issue Reproduction Repo - https://github.com/vikrantnegi/FlashMessageDemo

Preview -

Android Emulator Specifications -

Edit - Happens on my Android device as well

[lucasferreira]

Hi @vikrantnegi

I see it now that you are using the "floating" mode. So knowing this I'm able to reproduce your issue and you are totally right there are a extra spacing inside bottom of flash message in floating mode.

I will fix that ASAP and warn you to test the new fixed version.

[lucasferreira]

@vikrantnegi

I just published a new version of this lib in NPM, the version is 0.1.14 that fix you issue.

Can you upgrade in your project and test again?

[vikrantnegi]

@lucasferreira Thank you so much. The issue seems to be resolved. You can close this issue.