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.
Related
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.
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 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?
What do I do about this?
Xcode launches the app on the device and it starts up, but when it has started the image below pops up and when I click "OK" it crashes the app.
The simulator has no issues, but I cannot read the console in regards to debugging because of this. There really is not a reason why this should be happening.
Also I have no idea what code could cause this. I have no errors or warnings and everything has been fine right up until yesterday.
If there is any code or more info you need to help me with this, please ask:-)
I have removed the app, restarted the devices and my mac.
Ok I found the answer here:
Same issue here
Basically you can't do debugging on a Ad-Hoc profile:-)
Our latest app was rejected by giving following reason
"when the user launches the app, a blank black screen is produced"
We had tested this many times and did not notice this issue. We tested again now, but it is working properly for us.
Can someone help us to find out the issue?
I don't think anyone can help you find this issue, My suggestion would be to follow up with the Review Team and try to obtain as much information as you can from them. Such as, what device was it tested on, what OS version and so forth.
Ah, the many woes of the app store process.
Make sure that you have tested your app not only on the simulator but also on a physical device.
Secondly the issue might be that you have made some (false) assumptions about the data on the device, that you might have put there manually, but isn't handled when installing anew.
Therefore a plan of attack might be to remove the application complete from both device and simulator and try running them from a fresh install rather than on top of an already installed installation.
Best of luck!
Try to build and install your app from a clean state. You may not be seeing the same as the reviewer, because if you only "build&run" all the time, old files, which are not part of the final build, are still present on your device or in the simulator.
So clean the build folder, remove the app from your device, and try again. Also, check if you app can live without an internet connection.
Your best bet is to discuss this directly with the Apple guys (Resolution Center).