Under Review
over 1 year ago

SERIOUS BUGS - SDK 4.2.1

Building with SDK 4.1.7 my app looks and acts as expected. My current release on the app store is built with this SDK.

Building with SDK 4.2.1 most of the graphics on my app do not appear as they have up till this SDK release.

Also... when building with this SDK pressing the START button gets no response.

Very serious indeed.

I've attempted to include screen shots from the simulator for both SDK builds but I'm receiving an error message from the forum that says "The selected file is not allowed due to file quota restrictions". There's a message at the bottom of the editing window that says "Add images and other files by dragging them into the editor". Maybe that will actually work. Using the Insert function in the editor did not.

No.... same error.

Removing images to try again.

I guess the editor has been broken along with the SDK and developer statistics.

Jeff
  • over 1 year ago

    Also just reconfirmed that 

    if( self has :fnName )

    {       self.fnName();

    }

    does not work when building with SDK 4.2.2, or 4.2.1 and does work with SDK 4.1.7

    No compiler error or runtime error other than the if( self has :fnName ) is never true.

  • over 1 year ago in reply to Jeff

    I just reconfirmed this problem with calling MyViewBase.onUpdate() using SDK 4.2.2

    Suspecting something fishy about the onUpdate() I made a copy of the code in MyViewBase.onUpdate() and called it MyViewBase.showBasics().

    The views that are built on MyViewBase and call MyViewBase.showBasics() draw all of the fields as intended and show the diagnostics indicating entry and exit.

    The views that are built on MyViewBase and call MyViewBase.onUpdate() do not draw the fields, and do not show the diagnostics indicating entry and exit.

    In my case at least, the problem is not graphics... those work.

    The problem is something strange going on with calling onUpdate().

    To be clear... calling onUpdate() works as expected when building with SDK 4.1.7.

    It does not work when building with SDK 4.2.1 or 4.2.2

    I now have a work-around, but something very strange is going on with the handling of an inherited onUpdate().

    2 more hours into debugging SDKs that don't work as expected.

  • over 1 year ago

    SDK 4.2.2 displays the problems of 4.2.1

  • over 1 year ago in reply to Jeff

    I've found the same behavior with onShow(). Ending my efforts with 4.2.1 until it works like 4.1.7

  • over 1 year ago in reply to _psx_

    After investing about a day into trying to work with 4.2.1 I'm drawing the same conclusion. Reverting to 4.1.7 until the bugs and mysteries in 4.2.1 get sorted out by someone who is paid to do that.