Menu

#5 App closes immediately if the first screen opened contains an expiration

Beta
closed-fixed
None
5
CUCM
9.2(3)
1.0.0.0
1.0.5998.26348
2016-06-03
2016-05-13
No

If application is not running when an alert event with expiry comes in, or if the first page loaded has an expiry, the application is immediately closed. Issue is seen on 7975 with 9.2(3) firmware, but the message stays up on the 9971 tested with that runs 9.4(2)SR2 code.

Issue exists on SCCP code 9.2(1), 9.2(3), and 9.4(2)SR1 (latest)
Issue seems to only affect 79xx phones

Discussion

  • bcstechnologies

    bcstechnologies - 2016-05-13

    Same behavior is exhibited when trying to open certain screens from services, so this is related to launching the app in general for SOME screen types and NOT just the pushing. Changing title to reflect. Note that in testing so far, the "lighthing" screen type and "^customalert" are impacted. Conversely the "clock" screen type is not.

     
  • bcstechnologies

    bcstechnologies - 2016-05-13
    • summary: Pushed alert message immediately disappears if app is not running --> App closes immediately if the first screen opened contains an expiration
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1,4 @@
    -If Application is not running when an alert event with expiry comes in, the alert is immediately dismissed. Issue is seen on 7975 with 9.2(3) firmware, but the message stays up on the 9971 tested with that runs 9.4(2)SR2 code. Going to upgrade 7975 to test with newer firmware
    +If application is not running when an alert event with expiry comes in, or if the first page loaded has an expiry, the application is immediately closed. Issue is seen on 7975 with 9.2(3) firmware, but the message stays up on the 9971 tested with that runs 9.4(2)SR2 code.
    +
    +Issue exists on SCCP code 9.2(1), 9.2(3), and 9.4(2)SR1 (latest)
    +Issue seems to only affect 79xx phones
    
     
  • bcstechnologies

    bcstechnologies - 2016-05-13

    WORKAROUND: Disable screen expiration timer

     
  • bcstechnologies

    bcstechnologies - 2016-06-03

    Resolved in version 1.1. The application handler UPDATE which was designed to ensure when an inactive screen was restored the content was refreshed, was also firing when screens were loaded for the first time. This combined with the Softkey:Exit refresh destination caused the behavior seen in this bug. The application handler has been disabled, and other means of ensuring content is fresh are being implemented and considered.

     
  • bcstechnologies

    bcstechnologies - 2016-06-03
    • status: open --> closed-fixed
    • Fixed In: --> 1.0.5998.26348
     

Anonymous
Anonymous

Add attachments
Cancel