-
Notifications
You must be signed in to change notification settings - Fork 22
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
Custom Image in Bubble Icon Not Displaying in physical devices #18
Comments
Hi there, welcome to Dash Bubble! 👋🏻 I'm glad you're interested in contributing to this plugin. It's a great way to learn more about the codebase and to help grow the Flutter community 💙 Your issue will be reviewed by the maintainers and worked on as soon as possible. If you have any questions or need help, feel free to reach out to me @moazelsawaf. I am always happy to assist you 💙 Happy Coding! 😊 |
This issue has been open for 14 days without any activity 😔 If you're still working on this, please remove the Otherwise, we'll consider this issue stale and will close it in 7 days ❌ |
Still looking for a solution. |
I'm experiencing the same problem. It looks like the developer won't be helpful. I've been waiting for a solution to this issue for a while now. |
@tolgaakcaoglu, For now, the only workaround I can do is to replace the initial package bubble image that can be found in |
same issue on physical devices |
You're right. I also solved my problem using this method. The package owner forgets to be helpful. The custom image error of the package needs to be fixed. In addition, I would be very happy if they could do the following;
|
Hey there,
I'm encountering an issue when displaying a custom image within the bubble's icon attribute. When I set the
bubbleIcon
attribute to a custom image path, a black box appears instead of the image. However, the default icon provided by the package works perfectly.The icon is set as an image file placed inside:
android\app\src\main\res\drawable\
Result on a physical device:
PS: The custom image works fine on the virtual emulator.
Please help identify the issue.
The text was updated successfully, but these errors were encountered: