When I view the device log in Visual Studio when trying to debug my app which runs in the background (so no normal debugging is available) I get empty messages.
I am using Debug.WriteLine with the defaul System.Diagnostics, no custom stuff whatsoever. Tried restarting everything, but that didn't help. It does hit the lines because the code is executed and I see the empty message lines so it is partially working but the most important info is not visible.
It works fine on an iPhone 4S (iOS 9) but since today I'm using an iPhone SE (iOS 10) and the message is empty.
Doesn't make life easier not being able to debug and not being able to view the debug text :(
Any idea anyone?
Cheers,
Rob
screenshot
So yes, this does appear to be a bug in Xamarin.iOS. Bug filed:
https://bugzilla.xamarin.com/show_bug.cgi?id=52308
This is a regression in the latest Stable and Alpha/Beta releases (works as expected in the last stable release, Xam.iOS 10.2.1.5)
Xamarin engineers will now discuss this issue on the bug report. If you would like to receive a notification when the bug is updated, you can add yourself to the CC list for the bug. Please note that you will need to create an account on that system if you have not already done so.
Related
Odd one this. Ever since upgrading to iOS10 and the latest Appcelerator SDK (5.5.0), I can't get even a simple console.log("hi!") to show anything in the console when I'm testing on an iPhone 6s Plus connected to my Mac via USB, using LiveView.
I've tried changing it to Ti.API.info("hi!") - which I believe is the old way to do it - to no avail. If I change it to alert("hi!"), that works fine. However, it's not as useful as console.log used to be when developing things which MUST be tested on a connected device (the camera, in my case).
I've Googled this, plus done extensive searching on StackOverflow.
It may be that this is so new that no-one has noticed yet.
Can anyone help?
It's a known issue. Apple changed something with the way they log data. The Appcelerator SDK has to be adapted to this changes. I'm pretty sure they'll fix it asap. You'll have to await an update.
Greetings
Edit: Here is the corresponding jira ticket (https://jira.appcelerator.org/browse/TIMOB-23786)
I desperately need to use the Safari console on iOS 7 to debug a site. I've hooked my iPhone (5) displaying the site to my Mac. I've started Safari (v6.0.5), gone to the Develop menu, and started the web inspector for the site I'm on. I can see the list of elements on the site, which confirms I'm inside the correct inspector.
From what I've read, the logs to the console should be displayed inside the Logs section, and from what I've found inside Apple's iOS Safari documentation, I should be able to view logs inside there. For me though, nothing is ever logged. I can't even access any variables or functions; when I type anything in (e.g. document.title), it just 'logs' exactly what I've written, with the text I've just typed still in the input field. However, typing something that causes the browser on the device to show life works (e.g. alert('hi'); displays the alert dialog box on the device).
Can anyone help? This issue we have is only happening on iOS, and there's barely any other way to find what's going wrong. Is this problem limited to iOS 7?
I can confirm that this is an iOS 7 issue. The console.log statement works fine when using an iOS 6 or below device, but with iOS 7 won't show at all :(
Apple == new Microsoft();
Only minutes after posting this I got logging to work again, not sure if this is required, but it seemed to do magic for me:
Connect iOS 7 device
Open XCode
Setup device for development
Connect using Safari
Presto, I can see log messages again?!? (Mind you, I had not made any code-changes)
I had the same problem, just after updating to iOS 7. The solution was to update safari to the latest version for developers, which is version 6.1.
I have submitted an update of my application to iTunes which I got it approved today. Lately I have downloaded it on my device from iTunes to check and I found one functionality is not working as expected.
Problem:
I have a UIScrollView in my app and has horizontal scrolling. After the update I am not able to scroll it. I restarted the app and then it starts scrolling but scrolling infinite horizontally. I know this sounds stupid.
Immediately I opened my project code and ran it on device to check the issue using development provisioning profile but it is working perfectly over there.
Can any one suggest me what can be the issue? Or how can I debug that what went wrong when I submitted the update to iTunes?
You give us very little to work with, but here are a couple of suggestions:
Make sure you're looking at exactly the same code
Make sure you're testing code built with exactly the same compiler settings. For example, usually when you're running from Xcode you'll compile in debug mode. Don't. Compile it in "release" mode (with all the optimisations switched on)
Don't worry about provisioning profiles; they won't be the problem
If it's affecting all iOS 5 and 6 devices, though, I do wonder how you were testing it? And how fundamental is the scrolling to your app? It did, after all, pass Apple's testing. Maybe it's only happening on your devices because it has some "junk" left over from your previous testing?
I've made an app (called BeSharp), tested it a lot, uploaded it to Apple AppStore, and now all users report that the pop-up menu I use (custom one) does not respond to clicks.
It does not crash, so I don't understand how to get some debugging done.
So, the question:
How can I debug release version?
Thanks in advance.
P.S. Please find below some promo-codes if you wish to test an app yourself:
FAYNW9XTTMPY
LYK7EYJYJM4E
T6FW34E4TL6J
NJ99R4E39WEW
PJ473MERJKTH
MK4EMXE9XFFW
LN7AFXHJN9YK
MTTKW4PMXPFP
KK9HE74MKFJL
X6PWPHERHMLF
E7P96NNNAAN6
N93FFTPPA366
T9JX6PMN9ELT
JP39XKTT4J6N
Y3Y4R643E6F3
33HWLF4PFJPA
7XYW7NAH7A63
JNP4EYJHKLN6
46KPNPYFYALJ
Thanks everybody for comments.
I solved the issue.
After inserting some NSLog into code, and running release version on real device, I have pinpointed the issue, and it was in custom button component - in 6.1 some Alpha test function works incorrectly.
So I just updated it and everything worked fine.
When testing my iPhone app I have found it incredibly useful to log information to the console window. I think it is amazing that I can send out an adhoc build to my co-workers and if they experience problems I am able to plug their iPhone into my mac and grab their console output. However, sometimes the console window is blank when we do this. Why is this the case? The code has been built with logging enabled. Besides that, it seems that the console output, when I see it, contains information about not only my app, but other iphone system logging.
Thanks for any insight you can provide.
It looks like if I restart XCode then the console gets populated properly. Must be a bug in XCode, but restarting seems to always work.
It seems to be a new bug in 3.2.3 - older versions worked fine.