Native Logging and Certificate Wizard Downtime
source link: https://www.tuicool.com/articles/hit/N32yYjI
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
I’ve been so busy with the book I completely missed a lot of things I should have blogged about and one such thing is the NativeLogsReader cn1lib which has been in the extension manager for a while now.
The NativeLogsReader cn1lib was created by Francesco Galgani to include native logging into the Codename One log. A lot of times we get on device failures that are really hard to track. In those cases we ask users to connect cables and try to view the native logs to search for clues. With this library you can see native output even without physical access to the device!
That’s really helpful when you’re tracking an issue that happens on an end user device.
Certificate Wizard Issues
We’ve had several cases of downtime with the certificate wizard lately and we are going through such a downtime right now. We are working on fixing it and hopefully it will be fixed by the time you read this…
However, I’d like to explain why these things happen. The certificate wizard connects to Apples undocumented system to support generating certificates/provisioning. It’s a system they have in place for xcode but it’s a bit flaky. We could just use something like webscraping in the worst case scenario but either way every time Apple makes a change we need to adapt.
A while back Apple made a change, we adapted relatively quickly but introduced a few regressions which were really hard to pinpoint as they relate to behaviors such as cookie policies etc. Things that work for our localized test cases sometimes fail as we scale them to the entire community…
Hopefully, this round of whack-a-mole will be over soon.
Book Update and 5.0
As usual producing the book is taking way longer than planned but I’m getting there. I’m really excited about what we have so far and can’t wait to share it with you guys.
On a related subject we also need to update Codename One to run on newer JDK’s 9/10/11 all of which broke so many documented features in the JDK that we depend on. This is crucial as JDK 8 will EoL in 2019.
With those two things in mind we decided to postpone Codename One 5.0 to September instead of its current July target. This will give us time to address these issues and give me a bit of time to do some "actual work" that doesn’t revolve around the book.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK