I am hoping that someone here has experienced this error while saving an attachement. There was no special implementation and I am getting the following react errors.
After refreshing, the files seem fine, but it appears disruptive to the user.
I have contacted Appsheet Support, however it is now at the point that I am finding their support process extremely poor bordering on incompetence.
Thanking anyone in advance experiencing this in the past.
Getting an error while using saving an Attachement Type Error id: 341876Stack: Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7B_flattenCa... for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Po ( https://www.appsheet.com/assets/535c840cf5c4b22beb9a05cd7b2239800ed03dd7a2df999b677c7362aa4bdb71.js:... )
at p ( https://www.appsheet.com/assets/535c840cf5c4b22beb9a05cd7b2239800ed03dd7a2df999b677c7362aa4bdb71.js:... )
at m ( https://www.appsheet.com/assets/535c840cf5c4b22beb9a05cd7b2239800ed03dd7a2df999b677c7362aa4bdb71.js:... )
at https://www.appsheet.com/assets/535c840cf5c4b22beb9a05cd7b2239800ed03dd7a2df999b677c7362aa4bdb71.js:...
at Aa (https://www.appsheet.com/assets/535c840cf5c4b22beb9a05cd7b223980
@WillVerkaik wrote:
I have contacted Appsheet Support, however it is now at the point that I am finding their support process extremely poor bordering on incompetence.
This is disappointing to hear. It seemed Support was on a good track to turn things around from what it once was.
I'll get some eyes on it! Thanks for flagging!
Hey there, let me see if I can get this escalated to a support manager to look at your case. Would you mind sending me via PM any incident numbers you've received?
[4-2843000034578]
Support has come back to me and have escalated with appologies.
I discovered how to get rid of the error. I had originally used the large Card layout. Under Subheader I had used the Attachment Field.
Once I replaced the Layout to a Table, the error stopped. It is plausible that the react code was choking on the configuration to support this use case. That being said, I have not yet gone back to replicate, and have notified Support of my findings.
User | Count |
---|---|
15 | |
12 | |
8 | |
8 | |
4 |