-
Notifications
You must be signed in to change notification settings - Fork 43
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
[Bug]: Button click event change value in input form #1473
Comments
@pierre2202 we just published LVN Go for MacOS 0.3.1 that included the 0.3.1 release of the client that I think will solve this problem. Can you confirm your LVN Go version to see if this resolves your issue? |
i updated with the last version 0.3.1 all liveview native but the problem is always here, i did a mix deps ,compiled and relaunched the server |
can you share an example app for us to quickly diagnose? |
of course link of the app user_login_live.ex |
i tried a swift method ,that work better with lvngo ios but sometimes not . In macos that dont work. back end
|
@pierre2202 unfortunately Carson (our Swift dev) was dealing witth Hurricane Milton and lost power. I'm hoping he'll be back next week and I'll have him take a look at this. I did take a look at the app you linked but it was very large. It would be helpful if you could isolate this issue in an example app that only has the relevant code. Thanks! |
no problem i did that, the exampleapp is uploaded with only the user_login_live.ex on http://localhost:4000/ when server is launched |
What happened?
Hello , when i click on the button in macos lvngo the value doesnt change all the time,
in ios lvngo the first time value dont change but after the value change with a gap.
The problem is only in a form.
if i write this code all is ok but that is not normal
Library Version
last
Xcode Version
last
Swift Version
last
On which device or simulator are you running into the problem?
iPhone, MacOS
Target Device Operating System Version
last
Relevant log output
No response
The text was updated successfully, but these errors were encountered: