-
Notifications
You must be signed in to change notification settings - Fork 28
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
Bad behavior from Pasteboard plugin #179
Comments
It seems like a framework issue. Is it fixed or should we move this to the main repository issues @AleCGames ? |
I haven't tested further; I simply made a change in my code by executing pasteboard = require("plugin.pasteboard") right before using the plugin, so that the notification doesn't show at the start of the game. Initially, I was calling the plugin from the beginning of the game. I'll make a build by undoing the change and let you know the result to see if it's already fixed. |
I'm mainly asking this because it's probably a better idea to create a new issue in the main repository instead of the documentation repository. The issue will get more attention this way. |
Sure ... It was a mistake to posted it here. Thanks for the clarification. |
I have been able to confirm in my apps that when using the
plugin.pasteboard
, the first time the app is opened (this does not happen in subsequent sessions), in the scene where the plugin is required (local pasteboard = require("plugin.pasteboard")
), the app displays a toast notification saying "MyAppName pasted from your clipboard."This message suggests that the app is reading information from the clipboard, when in reality it is simply loading the plugin at that moment. This behavior is critical for our apps, as I already received a complaint from a user claiming that my app was reading clipboard information and could potentially steal sensitive data (without their consent), such as their credit card number, address, etc. I do not know how to fix this issue since Solar2D does not provide any information about it.
This behavior only occurs on Android.
The text was updated successfully, but these errors were encountered: