Crash when calling Notify

6 posts, 0 answers
  1. Oliver
    Oliver avatar
    36 posts
    Member since:
    Apr 2011

    Posted 21 Jul 2013 Link to this post

    protected override void OnNavigatedTo(System.Windows.Navigation.NavigationEventArgs e)
    {
        base.OnNavigatedTo(e);

        try
        {
            rateReminder = new RadRateApplicationReminder();
            rateReminder.RecurrencePerUsageCount = 1;
            rateReminder.SkipFurtherRemindersOnYesPressed = true;
            rateReminder.ReminderClosed += OnRateReminderReminderClosed;
            rateReminder.AllowUsersToSkipFurtherReminders = false;
            rateReminder.Notify();
        }
        catch (Exception)
        {
        }
    }

    The code above crashes with a COMException. Any suggestions? I'm on the latest official build.
  2. Deyan
    Admin
    Deyan avatar
    2038 posts

    Posted 24 Jul 2013 Link to this post

    Hello Oliver,

    Thanks for writing and for sharing your code.

    We are currently not able to reproduce the issue on our side. Could you please isolate the case in a sample project and send it to us for further investigation? If that's not possible, could you please describe the scenario in simple steps so that we can try to reproduce it here?

    You will have to open a new support ticket in order to be able to attach files in case you want to.

    Thanks for your time.

    Regards,
    Deyan
    Telerik
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
  3. DevCraft banner
  4. Oliver
    Oliver avatar
    36 posts
    Member since:
    Apr 2011

    Posted 26 Jul 2013 Link to this post

    In fact the call crashes with an InvalidOperationException: ApplicationRuntimeHelper should be initialized before using this component.
  5. Todor
    Admin
    Todor avatar
    778 posts

    Posted 29 Jul 2013 Link to this post

    Hello Oliver,

    Please have a look at the documentation article here, which explains how to initialize the ApplicationUsageHelper.

    Let me know if you need additional assistance.

    Regards,
    Todor
    Telerik
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
  6. Waleed
    Waleed avatar
    1 posts
    Member since:
    Sep 2008

    Posted 09 Oct 2013 Link to this post

    Hi,
    I confronted the same problem. Initialization  of ApplicationUsageHelper solved the problem

    Private Sub Application_Launching(ByVal sender As Object, ByVal e As LaunchingEventArgs)
        ApplicationUsageHelper.Init("1.1")
    End Sub
     
     Private Sub Application_Activated(ByVal sender As Object, ByVal e As ActivatedEventArgs)
        ApplicationUsageHelper.OnApplicationActivated()
    End Sub

    P.S: The value of version number didn't affect the workability of the app.
  7. Todor
    Admin
    Todor avatar
    778 posts

    Posted 14 Oct 2013 Link to this post

    Hello Waleed,

    Yes, the ApplicationUsageHelper must be initialized before using RadRateApplicationRemider. It is an application component which is also used by other components, for example RadDiagnostics. When RadDiagnostics reports that an exception has occurred, the report contains the version number that you have used to initialize the ApplicationUsageHelper. This information can help you identify which was the version that crashed so you can easier find the cause for the issue.

    Regards,
    Todor
    Telerik
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
Back to Top
DevCraft banner