I am executing my mobile scripts across an AWS device farm. During Execution the app is being invoked but all of a sudden the app is getting closed. And I also observed Key Pad is not getting enabled when script is under execution in the AWS device. How can I solve this issue? Kindly help me out..
I work for the AWS Device Farm team.
The logcat from your run should point out why the app crashed. It will give you the stack trace why it is getting closed suddenly. If you share the run URL from the console we can take a closer look. Most likely it is an app crash.
Device Farm does not introduce any code with your test scripts or app execution so it does not activate or deactivate the key pad as this is not a configurable item.
Again if you share the run URL we can take a look at these errors and update this answer accordingly.
Related
My flutter app works fine on debug and profile builds but crashes on release build. I would like to understand why it crashes on release build. Is there any way to see exceptions like I can see in debug mode? It is not enough to see print logs which I can see print logs and does not help. I need to know where and why the app crashes. So it would be helpful if I can see exception logs. I suspect insufficient pro guard rules causes this problem but I don't know which rules should I add more. If I can see exception log, this would help me to add correct rules to pro guard.
Connect your physical device or use any emulator and then run your app using this command flutter run --release from the terminal. You'd be able to view the logs in the release mode
I suggest to use third party tool to track production exceptions. I recommend Sentry (I am not employee, just happy user) as it is easy to configure and works out of the box.
Check https://pub.dev/packages/sentry package and https://sentry.io/ for documentation.
Please note that Sentry works ONLY at production. Also note that if your app crashes, the error is logged next time you try to open the app, and not immediately after the crash.
I have 5000 devices enrolled with EMM using android management API and recently I am getting issues with multiple devices out of nowhere and getting and error prompt after scanning the QR code on re-enrollment. All of my enrolled devices are Samsung Tab with the older version of android(7-9) and the issue doesn't seem to be related to the android version. Also, The issue has been experienced for the device which was earlier enrolled and was working fine but recently has this issue, we tried re-enrolling it but it gives us the same following error prompt after QR scan.
Cannot create a work profile - The security policy prevents the
creation of a managed device because a custom os is or has been
installed on this device
For your kind information, there is no custom os installed on the device and the device is not rooted or bootloader is not unlocked. I have researched a lot over the internet but cannot find a solution to the problem I have tried following approaches but it doesn't seem to work in my case
To fix this, you will need to update the time on the device by either connecting to wifi or cellular data (insert SIM-card), or by manually changing it in the set-up screen. After this is done you will be able to provision the device.
Tried DPC Identifier method for enrollment, When prompted to sign in on fresh factory reset device, enter afw#setup, which downloads Android Device Policy. Scan a QR code or manually enter an enrollment token to provision the device.
None of the above seems to work for me, I have also seen that its an issue related to Samsung Knox version, so can anyone from Samsung or google help me debugging and solving this issue, will removing the Knox app from the device work in my case.
Eagerly awaiting for the response as most of my device has started getting affected with this issue, please let me know your thoughts and resolution on this.
Not sure if that's an option for you as you have multiple devices, but on my single device, manually downloading and installing "google apps device policy" resolved the issue.
Been a lurker for a while and posting for the first time
Work as IT helpdesk and found a fix for us (context below)
We use Azure, InTune and Samsung Knox
Needing to assign a Knox profile so an application installs and runs
How we fixed this
Unassigned Knox profile
Ran tablet normally, skipping setup of Google, Samsung account and security
Running Samsung updates until current (24th Feb 2021)
Reassign the Knox profile
Factory resetting through settings
run through the setup process
Error has stopped at this point
You can either use Wi-Fi or SIM Card Data for OS updates through Knox
I had the same problems and this is how i fixed it. I have Samsung Tablet Android 10 and need to set it up under Enterprise.
Straight out of the box, you expand the OS, set up Network connection and than type in the google gmail space: afw#mobicontrol. This Does Not install the custom OS. Once expanded the OS has all the bloated software in tact plus the Mobicontrol app. I kept getting an error 'Can't Create Work Profile because Custom OS is installed on this device'. I did a factory reset but did so by powering it off than using the Power Button and Up Arrow to force it to the Android Recovery Screen. There is a factory reset option to choose from. "This Does Not Work". It still keeps the bloated software in tact.
You need to expand the Android OS first than do a reset. Go to SETTINGS. than ABOUT. at bottom is a RESET option. Choose that. Choose Factory Reset. This will delete all those apps. It reboots. Now you can enter afw#mobicontrol at the google email screen and it will install the custom OS and works under Soti.
Reset From the SETTINGS and do a Factory Reset. Than type in AFW#MOBICONTOL and the custom OS will work.
I'm trying to deploy my first Windows Phone 8 app to my brand new Lumia 920, after getting everything up and running on the emulator, but I'm running into the following error during deployment:
1>------ Deploy started: Project: AudioFilteringPhone, Configuration: Debug ARM ------
1>Deploying C:\Users\<username>\Documents\Visual Studio 2012\Projects\AudioFiltering\AudioFiltering\Bin\ARM\Debug\AudioFiltering_Debug_ARM.xap...
1>Connecting to Device...
1>Optimizing for device...
1>Installing the application...
1>Deployment of application to device failed.
1>Error writing file '%FOLDERID_SharedData%\PhoneTools\11.0\Install\{29b31259-9af9-47a5-9891-c3098315d3d8}\AudioFiltering_Debug_ARM.xap'. Error 0x80070003: The system cannot find the path specified.
If I manually try to deploy using the Deployment tool, I get the same error. Does anyone know what the cause of this is and how to alleviate it? This happens even if I just start a new WP8 app and immediately try to deploy it, so it's something wrong with my environment, not my application configuration.
I had exactly the same problem, but solved it by simply rebooting the phone. No software updates were required.
It turns out that there were software updates that needed to be installed. If anyone knows a way to find out the names of the updates applied, I will post them here, otherwise all I can say is that I had to update to OS version 8.0.10211.204.
This also can be because of wrong USB cable or port. I have a long cable for charging which works with android devices, but doesn't with WP.
Or maybe using another USB port helped.
For some reason, I'm no longer able to connect and deploy to my wp7 device. Zune does not show the phone as being connected, despite the fact that it is connected and the phone shows that it's being charged ... and the wpconnect tool gives the following error:
Failed to connect to the device.
Ensure that the device is completely
booted and is connected to the PC.
(0x80070103)
I rebooted the phone, and I've deployed to it before, so it's definitely developer unlocked. I verified that my computer has internet access. Any other troubleshooting thoughts?
Hey, I run into this all the time. Simply restart your phone and connect again. Make sure you plug in and unplug the phone several times, waiting at least a minute if it doesn't work.
In short, it's temperamental, Keep trying.
Make sure that you have switched off WiFi and Bluetooth on your phone.
I have found that I cannot deploy when Wifi and Bluetooth are switched on - even though Zune is syncing music and other content in the usual fashion. The error messages are frustratingly unhelpful!
As a short term workaround try using the Application Deployment utility to deploy the xap file.
I had the same issue. When I changed the Project properties target OS to 7.1 it worked.
I had the same issue. Only restoring to the previous OS version helped me.
Also I would that it usually happens when internet sharing is turned on.
I think I finally found the problem!
When I had this problem a few days ago, I had been charging my phone (Lumia 900) using a faulty charger which keeps on getting disconnected. And now that I've changed the cable and charger, it started working again!
I had the same problem with my previous phone as well (HTC Mozart), and I had a bad cable back then, but never made the connection (geddit?) between the problem and the cable...
My theory is that when the phone is running on bad power supply/not getting enough power, it sets a flag in the registry, which throws that error.
Also, bizarrely I just found that if you have internet sharing turned on then it won't let you connect.
Any of above mentioned did not work for me. I had many different error messages (included the 0x80070103)
What did is this:
Go to https://dev.windowsphone.com, uregister your phone.
Launch registration tool ("C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\Phone Registration\PhoneReg.exe")
Unregister in tool from 2) too (if it is showing still as
registered).
Now disconnect phone and connect it again
Register phone in tool from 2)
I just deployed my app to my iPhone for the first time. Every time it launches it vibrates before running, and it runs fine. The build is a Debug | iPhone one of my app.
Any ideas why it vibrates when it launches and how to stop that? It's definitely not something I coded up and I don't have any exceptions or issues when running in the simulator.
The vibration happens when you build the application in debug mode, and run the application without a debugger waiting. The MonoTouch soft debugger vibrates to inform you that it couldn't find the debugger.
Running the app in Release | iPhone mode solves this.
The number of vibrations is used to notify the user of a problem setting up debugging at startup. The full list (that will be maintained as we expand or modify it) is here:
http://monotouch.net/index.php?title=Documentation/Debugging
As of today:
Device Diagnostics
An application compiled with debug mode that has been deployed on the iPhone will try to contact MonoDevelop on startup on the IP address and port that MonoDevelop had at the time of the build.
If there is an error setting up the debugger, it will vibrate one of more times:
One vibration: The application was compiled with debugging support, but it is unable to reach MonoDevelop on the specified IP address and port to setup stdout/stderr
Two vibrations: It is unable to parse the address configured.
Three vibrations: Could not setup stdout/stderr to the application.