After updating to version 2023.09 and packages to their latest version as per the release notes, I get a white screen now when launching, the onSolutionOpen() for our solution does not get executed either. There’s also no errors, or errors in the console. Just wondering if anyone else is encountering this issue.
On creating a new solution ‘onSolutionOpen()’ works for me.
But I have another problem:
Calling “plugins.dialogs.showInputDialog(‘New Pin’, ‘input Pin:’);” throws this error in the console:
ERROR org.sablo.BrowserConsole - 16:27:9 ERROR ServicesService - sbl * Error (follows below) in in executing service Api call “showInputDialog” to service dialogs
at SabloService.buildStackMessage (http://localhost:8183/default-src_ngcli … s:28018:15)
at Object.apply (http://localhost:8183/default-src_ngcli … s:27833:36)
at http://localhost:8183/default-src_ngcli … s:28121:18
at _ZoneDelegate.invoke (http://localhost:8183/polyfills.js:502:158)
at Object.onInvoke (http://localhost:8183/vendor.js:46141:25)
at _ZoneDelegate.invoke (http://localhost:8183/polyfills.js:502:46)
at Zone.run (http://localhost:8183/polyfills.js:287:35)
at http://localhost:8183/polyfills.js:1363:28
at _ZoneDelegate.invokeTask (http://localhost:8183/polyfills.js:529:171)
at http://localhost:8183/vendor.js:45819:49
ERROR org.sablo.BrowserConsole - TypeError: values[0] is not iterable
at http://localhost:8183/default-src_ngcli … js:475:127
at Generator.next ()
at asyncGeneratorStep (http://localhost:8183/vendor.js:68846:24)
at _next (http://localhost:8183/vendor.js:68865:9)
at http://localhost:8183/vendor.js:68870:7
at new ZoneAwarePromise (http://localhost:8183/polyfills.js:1515:21)
at http://localhost:8183/vendor.js:68862:12
at DialogService.showDialog (http://localhost:8183/default-src_ngcli … 3.js:476:7)
at http://localhost:8183/default-src_ngcli … .js:453:27
at Generator.next ()
I found a solution myself: adding an empty string parameter at the end fixes the problem:
plugins.dialogs.showInputDialog(‘New Pin’, ‘input Pin:’, ‘’) works
the input dialog stuff is i think already fixed by this case: https://support.servoy.com/browse/SVY-18631
ryan1680098789:
After updating to version 2023.09 and packages to their latest version as per the release notes, I get a white screen now when launching, the onSolutionOpen() for our solution does not get executed either. There’s also no errors, or errors in the console. Just wondering if anyone else is encountering this issue.
what does the TiNG build console say? Did it really build your TiNG runtime?
You starting TiNG or NG1?
I am starting the NG client. On the build console there is nothing.
jcompagner:
ryan1680098789:
After updating to version 2023.09 and packages to their latest version as per the release notes, I get a white screen now when launching, the onSolutionOpen() for our solution does not get executed either. There’s also no errors, or errors in the console. Just wondering if anyone else is encountering this issue.what does the TiNG build console say? Did it really build your TiNG runtime?
You starting TiNG or NG1?
The build console just stays empty. And we’re starting TiNG
We’re getting this error when attempting to launch:
main.86e0a0a87d02bc29.js:1 ERROR Error: Uncaught (in promise): Error: JIT compiler unavailable
Error: JIT compiler unavailable
at dr (main.86e0a0a87d02bc29.js:1:166239)
at Ve.get (main.86e0a0a87d02bc29.js:1:276930)
at Gn (main.86e0a0a87d02bc29.js:1:143734)
at gl (main.86e0a0a87d02bc29.js:1:184802)
at main.86e0a0a87d02bc29.js:1:185074
at main.86e0a0a87d02bc29.js:1:166447
at Array.forEach ()
at Jo (main.86e0a0a87d02bc29.js:1:166411)
at gl (main.86e0a0a87d02bc29.js:1:185057)
at main.86e0a0a87d02bc29.js:1:185074
at Qt (polyfills.7236118f1f6bf221.js:1:17661)
at Qt (polyfills.7236118f1f6bf221.js:1:17153)
at polyfills.7236118f1f6bf221.js:1:18570
at tt.invokeTask (polyfills.7236118f1f6bf221.js:1:8649)
at Object.onInvokeTask (main.86e0a0a87d02bc29.js:1:281160)
at tt.invokeTask (polyfills.7236118f1f6bf221.js:1:8568)
at Gt.runTask (polyfills.7236118f1f6bf221.js:1:3909)
at st (polyfills.7236118f1f6bf221.js:1:10734)
i have no idea what that can be
there is no JIT compiler in the browser for Angular so that is correct, so i don;t know what he is doing there, haven’t seen that message before
So when you triggers once a build and clean, i guess in the build console you see that it is nicely build without any errors?
What kind of components/services do you use? Do you have your own stuff?
ah:
https://stackoverflow.com/questions/687 … lar-update
do you use some older components that are not updated to angular 13+? because view engine components are not supported anymore with angular 16+