-
I've got an acap that had no issue using paramConfig and the structure within it to control settings from the basic app UI "3-dots" interface up until recently when i upgraded firmware to 11.9. Worse is that all i get is the toast top right saying "Oops". Nothing even shows up in /var/log/info.log. Can anyone point me to what might have changed or if there are limitations i wasn't aware of? Here's an obfuscated version but it's basically what all examples use and what mine did as well up until recently when lots of root priv stuff started to change.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Did u try to Compile it with newer schema Version and or sdk to see If there any issue During build, on build also manifest is checked. When there is an issue you would See it. I Had this kind of issue also but it was my fault because I called an axparam func in the callback or other blocking things. |
Beta Was this translation helpful? Give feedback.
I did not, but looks pretty interesting and is now on my list to learn for the week :).
It turned out being my app name, i had an "_" between two words and the vapix API seems to turn those into "." when you do the update on param.cgi and need the root. notation.