I'm unable to print to my printer simulator...
Here's what I've done:
Found Printer Simulator
https://developer.apple.com/download/more/?=for%20Xcode
download and install Additional Tools for Xcode (Latest non-beta version)
Open the resulting Hardware folder and then the Printer Simulator
Try printing to one of the printer simulators while watching the printer log (I used my mac)
I got an error when trying to print.
[05/Feb/2018:09:24:38 -0600] [Client 1] Unable to encrypt connection from 192.168.10.108: Unable to find server credentials.
I looked at this question but no luck.
Tried removing /private/var/tmp/printd
I didn't have printd in the directory
Ensured I only have one network connection (wireless)
I found at least a workaround:
Because the log of the print simulator says, there was a problem with something about encryption, I looked out for a print option without encryption. And there is!
When you add the printer, you can select which type of communication protocol or whatever you'd like to take. Default is "Secure AirPrint". However, you can select "AirPrint" (You can even select special drivers. Probably, you won't have any problems with the right ones, but I didn't try). And that works!
There's one bad thing: I got on this problem while testing printing from the iOS Simulator. There, you can't (or it seems like you can't) choose between "Secure AirPrint" and "AirPrint". So I'm still looking for the final solution....
Related
This question is similar this question, but slightly different.
I am trying to retrieve the name of my currently connected wifi network using the Connectivity Plugin.
This answer works perfectly fine in android, and while it sounds like it should work for iOS, I am getting an exception:
PlatformException(UNAVAILABLE, wifi name unavailable, null)
Simple ex. of the code causing the exception (with the assumption I am connected to wifi, also not using an emulator):
Connectivity connectivity = Connectivity();
print(await (connectivity.getWifiName()));
My gut is telling me it may be permission related, but honestly I am not sure.
Cheers and thanks!
Edit:
I just realized, the exception above is thrown by the wifi plugin, which I was also experimenting with.
print(await (Wifi.ssid));
Connectivity simply returns null...
I'll see if I can fix that in the plugin's code. If so, I'll get back to this answer.
However, for now, adding the capability to your project (or simply switching it ON) on Xcode will do it: (no code change in your app required)
# on your project folder, run:
open -a xcode ./ios
In Xcode 12+
On Target > Runner > Signing & Capabilities, use the + Capability button to add the Access WiFi Information capability to your project.
In older Xcode versions
On Runner > Capabilities, switch Access WiFi Information to on.
See:
I'm looking for logs of the Xcode application itself. Not logs of my iOS app or device.
I've been doing a bit of experimental work with the storyboard source code xml. Sometimes I'll get a random crash of Xcode or a message like "The document Main.storyboard' could not be opened. Could not verify document content" (This is not git conflict related)
I'd like to look in the logs to see if it gives a clue as to what part of the xml is causing these crashes or errors.
Note: I was able to find some additional crash information by looking in the 'console' app. But not error information.
Thanks.
There are a few things here. First of all, I do not believe Xcode writes any dedicated log files (as opposed to, say, Android Studio, that puts logs under ~/Library/Logs/AndroidStudio2.2). Having said that, there are a couple of places to get them:
1. The device logs
Xcode uses system logging to log its messages to the console. If you open the Console app, find your macOS device in the Devices list and look at the messages. By default, it shows all the messages from all the apps, but you can filter our by PROCESS - Xcode (filtering is a bit unintuitive, you first search for Xcode which generates ANY|Xcode filter, than you select ANY and change it to PROCESS).
The one problem with the Console app on macOS Sierra is that it only shows logs from when you started the Console app, not earlier. You can use the log command line to collect previous logs (e.g. sudo log collect --last 1d). You can find more information about it here.
Alternatively, you can actually start Xcode from the terminal (by typing /Applications/Xcode-beta.app/Contents/MacOS/Xcode in the terminal window). If you do that, all the logs will be written to the terminal console.
2. The Diagnostic Reports
These (also accessible via the Console app) will contain crashes that Xcode itself doesn't log (there are some cases where Xcode will die silently, but the Diagnostics Reports may still contain the error along with the callstack and other useful info). Note that there are two places where Diagnostic Reports are stored, under ~/Library/Logs and /Library/Logs - make sure to check both.
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.
I know a lot of people have reported almost the same problem but i haven't found the solution yet.
I have eclipse installed.
Installed Kies on my computer to get the ADB driver for the phone.
I can see the ADBdriver on windows vista.
I put the galaxy in developer mode and USB troubleshooting mode.
The phone is detected in windows vista. I can see it in windows explorer.
If I run adb devices from the "cmd" it does list my phone.
But in eclipse it does not show up?
I have tried reinstalling the drivers a couple of times with no success.
Please help.
First off, I'm brand new to App development. I installed Eclipse, the add-on, plug-in, sdk, etc. and am following the book "Android for Developers, an App-Driven Approach" in the Deitel Developer Series.
I had the same issue... I could run the sample app in an AVD, but my phone wasn't showing up in the Android Device Chooser. Eclipse wouldn't see my connected phone, so I tried running "adb devices" from the command line in:
C:\Program Files (x86)\Android\android-sdk\platform-tools\
No devices showed up. I ensured the Galaxy was in Developer Mode with USB driver checked.
I could see the Samsung Galaxy S3 in Windows Explorer, and the Device Manager showed an warning with the driver under "Other Devices". I tried "Update Automatically" but that failed.
I went to this address:
http://www.samsung.com/ca/support/model/SGH-I747MBABMC
I downloaded KIES. Installation took a while (roughly 10 minutes)... it said it was installing a HotFix. Finally, I was prompted to choose items to install along KIES. I selected all three to be safe (Unified Driver Installer, Video Conversion Codec, and Kies Air Message). This took another minute or two.
When Kies came up, it said "please connect a device". I did so. Kies moved to a 'connecting' screen. After a bit, the Device Manager properly stated "SAMSUNG Android Phone" with "SAMSUNG Android ADB Interface device under it" (I'm assuming the driver was installed by Kies which caused the Device Manager to update). Kies still said "Connecting" but it wasn't proceeding so I closed Kies (the device manager seemed to indicate all was working now, and running "adb devices" worked)
It now showed up in Eclipse.
Looks like I did need Kies, and it fixed the issue.
Hope this helps others.
Worked for my S3 using Android 4.3
1. Download Kies 3 from http://www.samsung.com/us/kies/
2. Run it
3. Go to Tools > Reinstall Device drivers
4. My phone prompted my to allow USB debugging
=> The device showed up in Eclipse "Android Device Chooser"
I followed these steps to make it work :
Installed Kies -> Click on tools and 'install driver'
Went to device manager right click on the USB for the mobile device and ins
Followed this thread and got it to work. Initially it did not. Some points not mentioned.
1. When working it shows in the device manager as "Samsung Android Phone"
2. Initially it showed as unauthorised. Need to go to phone and on the popup message authorise.
Other things I tried.
1. In Regedit I deleted all usb mounted devices hklm/system/mounted devices
2. In Kies I reinstalled the drivers. tools/
3. After I installed Kies did a Windows Update. Nothing new
4. On the device in settings/general/development options I ticked "Show all ANR"
5. In settings/General/Security I unticked "unknown sources"
I am not sure if any of these had an effect but took 5 minutes and it was working. Go figure....
=========
Warning about deleting mounted devices. It switched my d: and e: drives around which confused the hell out of me.
Using the regedit delete hklm\system\mounteddevices (not the hard drives) worked for me.
After installing KIES I plugged my device in. I went to the device manager and my phone was in Others with an warning tag. When I looked at properties it said the device drivers was not install. In device manager I clicked on update drivers, using internet.
No changed.
In KIES I clicked on tools update drivers. It told me to remove my phone. I did and proceeded. After the update I inserted the phone again.
No change, the device manager said there were errors with the drivers installed.
I removed the device. dos prompt, regedit, navigate to hklm/system/mounteddevices and deleted all accept the harddrives. accepted warning.
I reinserted my phone and clicked on device manager. My phone was there with no errors, "SAMSUNG Android phone/SAMSUNG Android ADB Interface".
I started eclipse and clicked on devices and my phone was there with a question mark and label "unauthorised". I went to the phone and unlocked and accepted message about trusting this computer and ticked the "always" checkbox.
All was good, did a deploy, up and running.
I had this problem too with my windows 8.1 just like yours.
mine wont work with kies.
but I solved it.
some times my problem is gone worse when windows won't detect my Galaxy s3 at all even in Explorer! first I fixed this problem with install "Media Feature Pack for N and KN versions of Windows 8.1" from this link: here
but for your main problem i find Wondershare MobileGo application. with this you can see your phone on eclips device choser window and can run your apps on it.
you can find it from here!
if any buddy find a better way so let me know.
Before anyone just assumes what I am saying here, please read what I have to say.
I have read the hundreds of posts on this topic and have tried pretty much all the suggested resolutions, in no particular order:
Quitting Xcode
Deleting the derived data folder
Cleaning the project
Hard resetting iPhone
Resetting Mac
Tried a second iPhone
Different USB port
All these in 'special' order
Checked code signing attributes
"Validate Settings" returns no problems
Validation returns no problems
I am stumped when it comes to this. The only thing I can think of is actually resetting my phone, but don't see how this could help when it doesn't work on the second phone either.
Are there any other suggestions, tips, ideas on what could be causing this rather annoying bug?
UPDATE: The exact error:
Error launching remote program: No such file or directory (/Users/Username/Library/Developer/Xcode/DerivedData/ProjectName-dnfacjtdklqktcazrpfyupofdryp/Build/Products/Debug-iphoneos/ProjectName.app/ProjectName).
To get the error, I do any combination of the listed steps above, then click Run on "My Device" (an iPhone 4). Application never installs to the phone and Xcode reports the application has finished running then shows the above error.
My problem was cause by me accidently changing the "Deployment Target" (ios version) to a version higher than what was on the phone I tried to run the code on.
Change the deployment target to below or equal to the ios software version on your phone.
(this answer wasn't on your list) :)