1
Empty multiline input field with unwanted default value
planned
F
Fredx
runtime 4.5.7
appID 406671
page 7
build type preview (not relevant)
OS Win10 pro
Browser Chrome Version 104.0.5112.81 (64-bit)
When I set my input field property to multiline (true), some odd '41' value is displayed by default in the field during runtime, instead of the placeholder text. See attached pic.
Log In
K
Kirill Leventcov
planned
A problem has been identified, and the issue is now moved to the development.
T
Timo Kapanen
under review
T
Timo Kapanen
Hi Fredx and thanks for your report. How would I navigate to the problematic page in preview app? Best Regards, Timo Kapanen
F
Fredx
Save Details, Save Bank, then see the error in following 'Save Service' step (hidden until Bank is saved).
Is that what you asked for?
K
Kirill Leventcov
Fredx:
Hi,
I have checked your app and could not find anything on the AppGyver side that might be causing this. There are no 'initial' nor 'example' values configured, so the 41 should not be there.
Could you check that your Firebase project does not return the "41" somewhere by default?
F
Fredx
Kirill Leventcov: Hello Kirill, thanks for looking into the issue.
Please switch the multiline input option in the input field property to TRUE, this is when it displays a 41 value by default. No such default value when input field's multiline is set to FALSE.
So this is 100% not a firebase response issue.
F
Fredx
Kirill Leventcov: Hi there.
Has the team looked into this crazy bug?
When I create a new input field with multiline option as FALSE, no default '41', but that value gets displayed again when the multiline is turned on (TRUE). Sorry to be insisting, this is not a firebase error, if you reviewed the app carefully, you know the page does not GET any records, it is just plain inputs, so it cannot fetch any data from the outside.
The bug most likely comes from the input field component itself.
Let me know please...
K
Kirill Leventcov
Fredx:
I apologize for the delayed answer. We were able to reproduce the issue and identify a unique cause: 41 is displayed only in multi-line input that is attached to a POST data variable.
F
Fredx
Kirill Leventcov: Hi,
FYI. I saw the fix implemented for a few days last week, then back to '41' display bug this week. I guess you were doing tests and fix will be live later...
K
Kirill Leventcov
Hi Fredx:
A fix for this issue is not yet out, I will be informing here once it is ready. Thank you for your patience.
F
Fredx
Kirill Leventcov: Hi! The 41 digit bug is still there. When are you planning to fix this? It is impossible to release to public with such a display bug. It's been over 5 months, come on please....
F
Fredx
Kirill Leventcov: FYI, when I use the primitive input field instead with multiline turned to true, the number '101' is displayed by default.