Unable to add files to iOS real device using appium's pushFile method - appium

To automate a file upload scenario of a mobile application (iOS), I tried adding an image to the device which can be browsed using gallery during execution. I tried using Appium's pushFile method but I am not clear on what has to be passed to the first parameter of pushFile method.
I tried appium's pushFile method to add the image to device. The method takes two arguments. The first argument is the target path in iOS device. My expectation is to push the image to Files app on iOS, so I tried the format "#com.apple.mobileslideshow/profile.jpg". But it throws the following error.
An unknown server-side error occurred while processing the command. Original 
error: Failed to vend into the application documents. Error: InstallationLookupFailed
I referred bundle ids from here https://support.apple.com/en-in/guide/deployment/depece748c41/web

Related

Google Tag Manager for Xamarin iOS

I've followed the quick start guide here for setting up Google Tag Manager in my Xamarin.iOS app, but I am receiving an unexpected error when the container initializes:
GoogleTagManager warning: Error when loading resources from url: https://www.googletagmanager.com/r?id=GTM-XXXXX&v=iXXXXXXXXX status code = 403
I've tried two different valid container ids and they both fail with this error. Providing a random container id presents a different error message.
This error is caused by using a "Firebase (iOS)" container with the Google Tag Manager Xamarin component. At the time of this writing, the GTM component for Xamarin is only compatible with "Legacy iOS" containers. After switching to a Legacy iOS container, this error is no longer presented.

Build successful but unable to run on iOS simulator

I am making a demo of cordova app. The console log is showing me build successful but after sometime it shows this error and run fails :
2016-07-30 09:34:47.609 instruments[9268:1431174] WebKit Threading
Violation - initial use of WebKit from a secondary thread. Instruments
Usage Error: Unknown device specified:
"B7257830-92A2-4C85-A4BA-342D7237F9A8"
Known Devices:
test's iPhone (8.4.1) [7fdfcc5aaeb179fdb53a86343ba18796a1825bc4]
The error is to replace UDID with known devices but I am unable find the file where it is mentioned.
Please share the path of file or file name or anything related to this error. Thanks in advance.
I solved this error simply following two steps.
Step 1: Go to Run Options and select Run Configuration as image shown below.
Step 2 : Now a window will open as shown below & select your device from simulator list.

Parse.com 1.6 crash analytics upload failure

I have a problem getting the new crash reporting in Parse 1.6 to work. The symptoms are the same as parse.com 1.6 crash analytics not working , but my reputation is too low to add my information.
1) I followed the quick start and guide to set up crash reporting and upload my symbols
https://parse.com/docs/ios_guide#crashreporting/iOS
https://parse.com/apps/quickstart#analytics/crashreporting/ios/existing
2) I'm following the instructions to generate a crash report by running the app directly in the simulator (iOS 7-8) and on the device (iOS 6) without a debugger attached. On the simulator I can actually see the minidump being created in Library/Parse/PFCrashReports.
3) When launching the app again I get the message "Breakpad Uploader: unable to determine minidump file length" and the crash dump disappears from the file system. So I assume Parse uses google breakpad under the hood, and the error is created by Uploader.mm because the call to stat() fails. I tried the same call in my own code and it succeeds there.
My gut feeling is that there is either a permission problems, or some other code locks the file while the uploader tries to access it. As the parse libraries are closed source it is hard to check anything, though. It is a bit suspicious that other people don't seem to have a problem with this, which may mean some other settings or configuration problem.

IBM Worklight Application Center iOS unresponsive to touch events

After successfully building and deploying the IBMAppCenter project, when attempting to download the IBM Application Center on iOS devices, there is no response when clicking on the actual installer link. This occurs on both real devices and through the simulator. Android application seems to be working just fine. I've provided a picture here showing some of the errors messages that we're seeing when clicking on 'IBM App Center iOS', as well as provided a subset of them below (http://i.imgur.com/vLrhVjT.jpg):
Deprecated attempt to access property 'changedTouches' on a non-TouchEvent object.
Deprecated attempt to access property 'target' on a non-Event object.
TypeError: undefined is not an object (evaluating 'a.target.getAttribute')
...
Deprecated attempt to access property 'which' on a non-UIEvent object.
App Center Console version 6.2.0.00-20140613-0730
IBM Worklight Studio version 6.2.0.1
Any idea what may be causing this, and how we can correct it? Thanks!
Make sure you are using a recent iFix of Worklight 6.2.0.x containing required Dojo fixes in order to add support for iOS 8 (which you are likely attempting to use the app on).
You can review the following tech note for instructions on downloading and installing the iFix: http://www-01.ibm.com/support/docview.wss?uid=swg21684538

trigger.io Error reading file

I use the forge.file.saveURL to save a JSON object to the local file system, then I use forge.file.String to read the contents and display them on the device.
This works just fine on IOS and Android but it seem on Android after the device has closed the app or force closed it after being open for a while when I reopen the app and try and access the file I get the error message in the console
Native call file.string with task.params:
{"uri":"file:///storage/sdcard0/Android/data/com.phonegap.conbop/files/Download/594f9cdc-a791-40ef-a40b-75d16948a9ca"}
[DEBUG] Returned: {"content":{"message":"Error reading
file","type":"UNEXPECTED_FAILURE","subtype":null},"callid":"508FE1AD-EB74-4377-8FDA-AA7318457B5C","status":"error"}
I have tested the IOS and this does not seem to happen there, its almost like the file is getting corrupt or something but what is strange is a also use the file.saveURL to save images etc and those work just fine so I'm not sure why this one is having issues.

Resources