Failed to create session. An unknown server-side error occurred while processing the command. Original error: 'app' option is required for reinstall - appium

I need your help. I want to connect the device locally (not an emulator). enter image description here
But I stopped at this problem that I can't solve.enter image description here

If your app is not installed on the test device then you need to provide appium:app capability with the path to the *.apk file. If your app is already installed on the device then you can try adding appium:noReset capability with value true.

hey have you tried adding this capability?
desired_caps['appWaitActivity'] = '*'
for pycharm and
appium:appWaitActivity text *
into appiuminspector
this worked for me.

Related

This bundle is invalid - The Info.plist file for PersonalizedAdConsent.framework is missing or could not be read

The title error is what gets emailed after uploading the ipa via the application loader and below is the error that occurs in debug mode:
ERROR: "The framework
APPNAME.app/Frameworks/PersonalizedAdConsent.framework does not
contain a binary named PersonalizedAdConsent"
I've been getting this error in debug mode when trying to build the project. However, when I build it in Ad-Hoc mode, it builds fine and uploads on the application loader without any issues but then I get the following mail
"This bundle is invalid - The Info.plist file for
PersonalizedAdConsent.framework is missing or could not be read."
I've looked in the Info.plist file as well as .csproj file for this reference and I cannot find it anywhere.
Also searched online, can't find much about the PersonalizedAdConsent.
Any ideas?
So it seems like the issue was because of the following packages:
Xamarin.Google.iOS.MobileAds
&
Xamarin.Firebase.Ads
As far as I can tell, the app needs permissions to request consent to display ads or personalized ads (not too sure exactly) and it build correctly after removing these packages.
These were in a build that I've done on Windows for a different app which did not actually use them but VS for MAC gave me the issues and it turned out to be these packages that were causing it.
Hope it helps!

iTunes Store Operation Failed When Uploading App Inside Xcode Description Length Too Long

So when I go into Xcode -> Archive -> Upload To App Store I get this:
I have no idea how the description length is so long. Inside the Itunes Connect portal, my release descriptions are very short.
How do I change this inside Xcode?
I've tried using the Application Loader and other versions of Xcode but get the same error.
Any suggestions appreciated.
Your iTunes store operation failed due to two requirements not fulfilled.
You have enable the iPad multitasking, which requires the all orientations but you have enable only portrait mode, which is wrong. You have to enable all the orientations which is required and also mentioned in the error.
In your bundle "com.buildregs.Build-Regs" has only configured the portrait mode, you have to configure all the orientation into the this bundle id.
Also Update your Xcode the latest Appstore version. Do not use a beta version of Xcode and that will solve your second error.
When I have run into this stockoverflow page, I have tried all the steps but could not succeeded. My app was build with ionicframework and I was getting 2 errors. The first one was "iTUNES Store Operation Failed: description length" error and another one was complaining about image path is not wring for icon.png. After fixing image url error, this error didn't appear anymore.
I realized that I was using image.xcassets but I left icon bundle in the plist file, and this was, somehow, causing the description error as well. I simply removed icon.png line from plist file and I could upload binaries to ap store
I got this top two errors a little earlier and after two hours searching got that
Unity iOS build setting -> Resolution and Presentation ->
Multitasking Support (Requires Fullscreen: option was Inactive).
After Active this option all error gone.

App installation failed: Could not write to the device

In Xcode 6.3, I got this error when trying to run an iOS project written in Swift on a real device.
App installation failed
could not write to the device.
I tried to clean the project and run again, but the same error occurs.
How can I fix this error?
Deleting the app on the device and running the project again works for me.
I did a Clean and installed my app successfully.
Product->Clean(Shift-Cmd-K)
I turned off the device and turned it on again after which I did not get such error.
OK, few things you should consider that could guide us to the problem, please check and post the answers:
is your project using capabilities? are they set correctly (should be all green)
did you try with a different project (something really simple)?
are you able to install apps from the App Store?
did you check the amount of free space left in the device?
if not, another suggestion will be using exception breakpoint, there is someone that posted an explanation how to setup it, do it and post the logs
App installation failed
I hope it helps you
Got this problem twice in one week on complete different devices.
One device had no more storage left, after deleting some apps the project installed perfectly.
The other device was fixed after rebooting the device
If you are using a free developer account you may need to uninstall some other apps you have signed.
For me it was the provisioning profile - I used distribution instead of development
My issue was an embedded framework.
Go to "Build Phases" -> "Embed Frameworks" -> Check "Copy only when installing", and it got rid of the issue for me.
For me the following did not work on iOS 11 beta 10, XCode 9 beta 6:
Restart the device
Deleting the app from the device
No symlinks were in the project
There was plenty of storage available
Deleted Derived Data and voilá, it worked again
in my project this problem happened because there was a folder with symbolic link. I removed that folder and it worked properly.
This error has many potential root causes, as can be seen by the large variety of suggested answers. The best approach to troubleshooting app installation issues like this one is usually to inspect the console of the iOS device itself, as that'll often provide much more specific error messages. In Xcode open the 'Devices and Simulators' window and take a peek at the logs of the device where your app is being installed.
In my case, the "Could not write to the device" error was being caused by this:
Feb 27 10:54:58 iPhone-7-110 installd(MobileSystemServices)[46] : 0x16f92f000 -[MIBundle _validateWithError:]: 38: Failed to load Info.plist from bundle at path /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ebmR6U/extracted/SampleApp.app/Frameworks/SomeFramework.framework
Which clearly hints at what's actually going on. I had forgotten to set an Info.plist file for my dynamic framework target (used by the app).
I had a symlink in my project to a file outside of the project. When I deleted this symlink the install worked fine.
I was having the same error, i just deleted the project and fixed!
Go to Window -> Project and right click, and remove from projects!
In the case of your device have an app with the same bundle identifier, Xcode will throw this error.
Try to delete potential app with the same bundle identifier.
Check your provision profile, maybe you are using the app store provision profile like me. I had to change the app store provision profile to development, now it's working.
Tried all of the above answers: Deleting the app, clearing storage space, cleaning the project...
What finally worked was bumping the build number in info.plist (General > Build)
For anyone still facing this Issue:
There are so many reasons and this is one of them as it happened to me.
I've faced the same problem and I was connected wirelessly and If you are trying to install the application in wireless connecting mode (connected through same network), this might probably because of poor internet connection. Check your internet connection and try again, it works fine...
Get rid of embedded libraries, dont' just throw it in there make sure it is embedded indeed.
If you use your iPhone for debug, maybe, because your iPhone's storage space is less than your debug App.
Clean your iPhone --- Real machine
Clean your Mac --- Simulator
This looks like another time waster courtesy of Apple's amazingly high class development team. On iOS11 Xcode9 (pick your beta, any one works) this will happen randomly. Appears to be more frequent if you dare to switch apps while compiling. Just build again and stare at xcode - it'll work the second time without fail in my experience.
Apparently this message can also appear if the system clock of device where the app is being installed is too far away from the current time.
I was doing some tests with date formatters by changing my iPhone's system clock and eventually forgot to reset it to the current time. Afterwards it always displayed the same message ("could not write to the device.") whenever I attempted to run the app. Simply resetting the clock in Settings fixed the issue.
Nothing helped me. I followed the below steps,
Clean derived data folder
Quit Xcode and disconnect device
Restart Macbook
Restart Device
Open Xcode
Clean and run the project
Finally I got it working!!
I am facing same issue then solved out follow this step and now its working.
Deleting the app from the device
Try to install another application
Remove derived data in X-code.
Restart X-Code then clean and build the project then run.
It's still not working then
Remove un-used application
Restart the device and check the Available and capacity in settings
Again app run in device
I hope its worked, enjoy it.
My problem was I had initially installed the app using a different set of developer credentials on the device. Deleting the app from the device fixed it.
Maybe it can be due to the following error App installation failed. No code signature found. In my case after a project clean the description of the error switched to "No code signature found".
In my case I created two frameworks but they had the same bundle identifier.
This caused the installation to fail, so double check the frameworks bundle identifiers and make sure that each of them have a unique bundle identifier.
Environment: Xcode 10
sometime this error occurs due to wrong certificate.Please make sure your certificate.
Also this the error shown if your machine running Xcode is low on space.
Once I had to load an App Container for debugging purposes into an iPad, said operation failed because the container was too big (18 GB) for this device (16 GB minus the OS), so that I desisted the task and completly forgot about it, leaving the failed installation in the device. Later, when trying to install a different application this error appeared, once I got rid of the failed app installation, everything got back to normal.
Basically, your Ipad might be low in storage.
One reason this can happen is if your app bundle contains broken symlinks.

Error in binary file while adding permission

I am a newbie in blackberry, trying to build a application in native cascade c++.
I am using Momentics IDE and sdk(10.3.1). In my helloworld application I try to use the persmission by looking at the official document of blackberry
https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/topic/c_about_bar_app_descriptor_file.html
But I am getting error while running the app. I am using the simulator.
My error message
Error in final launch sequence
Cannot prepare and download the binary
Error: Could not obtain launch permissions
Please help me out.
Thank you in advance
Just a silly mistake: I figure it out that i have to run the simulator with "Run as Administration" and after it just have to give access the permission from the simulator.

Unable to open log for Persistent Connection, i.e. push log on iPhone

I have tried to enable push notification logging on my iPhone according to these instructions: Apple Technical Note 2265.
I have managed to install the PersistentConnectionLogging.mobileconfig file without any problems. When looking in the console window for my device, I get the following warning:
<Warning>: Unable to open logging file '/var/mobile/Library/Logs/PersistentConnection/com.apple.syncdefaultsd-syncdefaultsd-APSClient.log'
What does this really mean? It seems to me like that it is failing to create the logging file on my computer :(
I have created the path on my computer.
Has anyone encountered the same problem? Is it possible to set the path where the log shall be saved?
As it turns out, the logging via the Organizer does not seems to be working. According to the technical note, console logging is not available in iOS 6.x. However I could read the log using iTunes.
You must connect your device and synchronize it. After this the crash log should be found here (on Mac OS X):
~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>/PersistentConnection/
I hope this helps someone.

Resources