Android platform is badly broken on Tokyo :

-
Android platform is badly broken on Tokyo :

Bitmap no more displayed
https://quality.embarcadero.com/browse/RSP-17687

Application crash with 'Can not activate current context' exception
https://quality.embarcadero.com/browse/RSP-17189

Android class initialization limitation (segmentation fault)
https://quality.embarcadero.com/browse/RSP-15775

Android app made with Tokyo are super slow
https://quality.embarcadero.com/browse/RSP-17162

Android Mixing 2D(with ViewPort3D)/3D(with layer2D) Not Work
https://quality.embarcadero.com/browse/RSP-17673

Delphi 10.2 Tokyo (Mobile platform) - use the FmxObject.AddObject component will occurs image overlay problem
https://quality.embarcadero.com/browse/RSP-17663

TImageList saved in Berlin, do not show its imagens in Tokio at runtime in Android.
https://quality.embarcadero.com/browse/RSP-17654

TListView Performance Degraded when compiled with Tokyo
https://quality.embarcadero.com/browse/RSP-17652

Android Painting cannot handle bitmap canvas paints
https://quality.embarcadero.com/browse/RSP-17636

Android Application->OnIdle Failed
https://quality.embarcadero.com/browse/RSP-17177

Android Severe painting problems - Worked in Berlin Version
https://quality.embarcadero.com/browse/RSP-17173

...
https://quality.embarcadero.com/browse/RSP-17687

Comments

  1. Stefan GlienkeMarch 30, 2017 at 5:30 AM

    I really wonder why these issues were not found during beta given that some are even filed by third party vendors that should have access to beta from day one (except these were beta bugs being migrated into public system though).

    ReplyDelete
  2. Stéphane WierzbickiMarch 30, 2017 at 5:46 AM

    Are you sure that these issues were not found during beta ?... Some of them are so visible...

    ReplyDelete
  3. Lars FosdalMarch 30, 2017 at 5:48 AM

    Makes you wonder if there actually was a dedicated test team with a test plan, or just random spot-testers :P

    ReplyDelete
  4. Stefan GlienkeMarch 30, 2017 at 6:02 AM

    I am not defending Embarcadero Q&A though (I myself often enough ask how can something not be found before I do) or that beta testers are a replacement for their Q&A. However given that basically almost every Delphi customer nowadays has access to beta at some point "so visible" issues should be easy to spot before release.

    ReplyDelete
  5. Claudio PifferMarch 30, 2017 at 7:55 AM

    /sub

    ReplyDelete
  6. Dalija PrasnikarMarch 30, 2017 at 11:12 AM

    Beta testing is well, beta testing... it cannot replace alpha testing by the developer team and their Q&A, especially in such large product.

    It is impossible for each beta tester to go through all features and sufficiently test them. Even if time would permit it, not all beta testers use and are familiar with all technologies and features. So possibility that some features get very small coverage (or even none) is quite high.

    ReplyDelete
  7. Brian HamiltonMarch 30, 2017 at 11:15 AM

    I see via the forum that tanidicator (animated indicator to show the program is busy) causes a downstream problem for other controls and alot of the problems are related to the threading changes that were made

    ReplyDelete
  8. Alexandre MachadoMarch 30, 2017 at 2:54 PM

    The issue with beta as a test phase is: most beta testers don't test their real code base because of many external dependencies which are unavailable, most of the times. So beta testers are basically playing with simple demo applications where everything seems to work.

    ReplyDelete
  9. Jennifer PowellMarch 30, 2017 at 5:31 PM

    Nonsense Machado.

    There are serious program regiments for testing well beyond your so called simple demo applications. What? You think that the test regiment for releases of Delphi are just simply the demos that ship with the product?

    Now, whether QC engages in a full test regiment is another matter and that would include previous test regiments plus the new ones created for the new version.

    Of course, people that use Delphi for creating vaporware make those kind of statements, and naturally "beta" from
    that view is nothing more than a Greek symbol to them, really.



    ReplyDelete
  10. Alexandre MachadoMarch 30, 2017 at 5:36 PM

    Interesting Jennifer Powell. I've been taking part on Delphi beta tests for a long time and I could never build any of my real world applications using it, because no 3rd party developer deploys their libraries ported to the new - still in beta - IDE, before the release date, or at least when the release candidate is ready. Besides libraries with no dependencies, I don't see how one can build a full real world application using a beta product.

    ReplyDelete
  11. Lars FosdalMarch 30, 2017 at 10:27 PM

    Alexandre Machado I have the same problem. And even if I had all the component packages, I can't say that it would be likely that I could spend working hours on doing a full test, since that is a three day task at minimum, involving multiple people. So, it is down to spot testing old known issues, looking for glaring flaws, and fiddling around with new features.

    ReplyDelete
  12. Nick HodgesMarch 31, 2017 at 6:31 AM

    Alexandre Machado If you have been taking part in Beta tests, then you should know that you aren't supposed to talk about it on public forums. Just sayin'.

    ReplyDelete
  13. Brian HamiltonMarch 31, 2017 at 11:58 AM

    huh? its not like he gave any information away that was like a trade secret or something

    ReplyDelete
  14. Stefan GlienkeMarch 31, 2017 at 12:15 PM

    Brian Hamilton Part of a typical Beta NDA is that you are also not allowed to tell that you are or were in the beta.

    That might make or not make sense given the fact that customers on subscription are able to participate in beta (see https://www.embarcadero.com/update-subscription) but that is how it is.

    BTT: given the fact that in the past many third party vendors that were close with Embarcadero (tech partner status) took weeks or months to release a version after a release leads me to the conclusion that Alexandre has a point here. However in my original post I was specifically addressing those third parties (tech partners) to be less sloppy and test their sh... stuff during beta. It reduces bugs and they have their things ready on day one after release.

    ReplyDelete
  15. Brian HamiltonMarch 31, 2017 at 12:18 PM

    yes, I do realise that, but, people are just going to get put off offering their time to be in a beta program, when they get belittled publicly like this (and instead Nick could have posted that they are working on the bugs or similar)

    ReplyDelete
  16. Dalija PrasnikarMarch 31, 2017 at 12:22 PM

    Brian Hamilton Of course they are working on the bugs... question is whether they are producing them of fixing them ;-)

    ReplyDelete
  17. Stefan GlienkeMarch 31, 2017 at 12:26 PM

    Dalija Prasnikar Works great when you have Q&A that gets paid per found and R&D per fixed bugs :p

    ReplyDelete
  18. Dalija PrasnikarMarch 31, 2017 at 12:28 PM

    Joking aside, most prominent bugs are always being worked on... main problem has always been how fast fixes will get out.

    ReplyDelete
  19. Lars FosdalMarch 31, 2017 at 12:57 PM

    Nick Hodges If you are a subscriber, you are per definition also a potential beta tester - or should we deny that?
    If we admit to being subscribers, are we then breaking an NDA? If we say that we - as subscribers - more often than not - do NOT have access to all third party packages with our subscriber accessible beta - are we then breaking an NDA? We are after all not talking about the beta it self, but the lack of third party components.

    To be flippant - These are not the NDA breaches you are looking for. :P

    ReplyDelete
  20. Alexandre MachadoMarch 31, 2017 at 4:44 PM

    Ok Nick Hodges my fault! I just thought that denying it is just like denying that I'm human, not an alien, you know... ;-) Besides that I'm not blaming Embarcadero for that. Just explaining how things are.

    ReplyDelete
  21. Eivind BakkestuenMarch 31, 2017 at 5:48 PM

    Alexandre Machado "No" 3rd party beta support is too strong. NexusDB made their libraries available during the beta, to customers that were also on the beta, as did a number of other 3rd parties (they can speak up themselves if they want). However it is true that some of the biggest libraries were not available (at least not via the Emb beta channels).

    ReplyDelete
  22. Irwanto IrwantoApril 5, 2017 at 5:23 AM

    oh my good

    ReplyDelete

Post a Comment