Subsequently, the User will access the site with his/her user-id (User's email) and password (hereinafter, "Codes") provided by you in the registration process. In order to use the Service, you must register in advance on the site by following the procedure laid down therein and provide the information requested. The User is obliged to carry out updates of its software for the entire duration of the services, where such updates are necessary in order to use the Service. The Company is not responsible for the delivery to the User of these tools, connections, devices and media, and is not responsible for any defects or malfunction of the same.
In order to access the Site and use the Service, the User must provide the tools, telecommunication connections, the equipment, the necessary hardware and software means needed, independently. The User is responsible for regularly reviewing the terms and conditions in order to verify the content of the same. The Company has the right to modify the Terms and Conditions at any time in the event of changes to applicable laws or if it intends to make changes to the Service. If you fail to approve the Terms the User shall not make use of the Service. In order to use the Service, the User must accept these Terms and Conditions during the registration to the site referred to in art. 1.1 (hereinafter "Service") is governed by these Terms of Service (the "Terms"). The service offered by the Company in the preceding art. 0000000000, email offers users (hereinafter, the "Users") the opportunity to make use of the services referred to on the web site (hereinafter "Site"). Using Package Flight, we've also shipped a version of the app with all async methods disabled to see if they're causing a deadlock, but nothing changed.TrainToSmile (Hereinafter, the "Company") located at Via dei Vanga, 73, VAT. It seems like the wtachdog is killing the app even if it's working properly. They're reported as hangs, but as I sad users don't experience any kind of slow down or hang before the app closes itself. In dev center we see this three main reasons for the crash:ĮM_WATCHDOG_TIMEOUT_DEADA444_0FF49CD6.(app_name)_h8pp9jtv6cete!(app_name).exe_Timeout_expired:_event_type_=_Show,_timeout_modifier_type_=_None,_server_task_currentState_=_Showing,_targetState_=_Active.ĮM_WATCHDOG_TIMEOUT_DEADA444_0FF49CD6.(app_name)_h8pp9jtv6cete!(app_name).exe_Activation_FailureĮM_WATCHDOG_TIMEOUT_DEADA444_bad_dump!missing_teb So we don't think that resources are the problem. But on a Lumia 650 on average at startup the app uses 30mb of Ram, max 20% of GPU and max. We've ran several performance tests to spot if the reason of the crash was any kind of resource limit. The others have no issues.Ĭrashes are present only in the ARM version of the app. This happens all the time and only to those users. On more powerful devices, like the Lumia 930, they're abile to reach the login page, on slower devices, like the Lumia 535, the apps closes itself while the splash screen is shown. Instead to other users with the same device and the same version of OS, the app, withoutĪny slow down or hang, continues to crash/close itself. We test the app (debug and release mode) on a Lumia 650 (last insider build - release preview) and a Lumia 950 (last stable build) and we experience no crashes or hangs. This happens only to some users and it's not related to the OS/device version. Basically on Windows 10 Mobile the app closes itself after a few seconds that it has been launched. We have a serious issue with our app that we aren't able to fix.
0 kommentar(er)
