I have a Metal-powered app that works just fine on my dev Mac, my main Mac and my friend's Mac. However when I send it to Apple, they get this awful glitch while resizing window. Here are their screenshots:
What on the Earth can cause that only on their macs?
Edit: I was able to retrieve system info from Apple engineers.
So I guess the problem is with either NVidia driver or non-Retina screen. Any thoughts on that?
Related
I have written an OSX 10.9+ app which works fine on all my test machines but two people with laptops have so far said the app opens (shows light under icon) but shows no window but will show the menu for the app with no drop down, it can highlight but does nothing else.
I can't for the life of me figure out why this is happening. I have checked Initial Controller is set in the storyboard. The plist looks ok. No complaints in console. Works on an old iMac from 2007, a Mac Pro 6 core and a New Retina iMac all with Yosemite.
Both cases where it doesn't open are on OSX 10.9.5
This is the screenshot of how it should look when opened:
The app is currently available for free, if anybody can shed some light on it I would be much appreciated.
https://itunes.apple.com/gb/app/bubble-tuner-realtime-chromatic/id972729737?mt=12
Thanks
Geoff
Storyboards are not compatible with OS X prior to v10.10:
NSStoryBoard Class Reference
Availability
Available in OS X v10.10 and later.
I experienced the same thing with a project; only nib/xibs work for OS X < v10.10.
This might be esoteric but here goes.
I'm developing a program in WPF for use on a multitouch screen. I'm using the Surface 2.0 SDK and trying to get the Toolkit to simulate inputs and run the stress test. However SurfaceStress.exe is throwing an error:
Error 0: Cannot get reference to virtual digitizer controller.
and Input Simulator is giving me a timeout error looking for the controller.
I've read up about it on MSDN http://msdn.microsoft.com/en-us/library/ff727911.aspx
I know it can't run two controllers at the same time and it's not on a SUR40. It says "Tablet PC Settings" would only appear if the Input Simulator is running. But it's running anyway and its Setup button is grayed out. I don't have a touchscreen but I do have a Wacom Bamboo tablet connected. Has anyone else had interference between a tablet and Surface Input Simulator?
It was in Device Manager. Bamboo touch drivers disabled the Virtual Digitizer Controller which was also listed as a device. Flip the switches and rode off into the sunset. good job, me! o/
I have created one application for iPhone. Application does a search for all watersports around the world. It is webservice based application.
My application runs smooth on Simulator without any crash report but when I create ipa file and launch same application on my iPod (I dont have my own iPhone) the application crashes after some time. Scenario of crash is not fixed so I assume this is because of Memory Leak or memory warning.
I used this function didReceiveMemoryWarning to identify memory warning but the function doesn't get called on simulator.
My Xcode version is 4.3 and unfortunately I updated the version of my iPod to iOS 6.0 so I can not test the app by connecting my iPod to the Mac. I am going to update my Mac and Xcode very soon but not soon enough to make this issue resolve/test.
Any ideas?
You can get the crash log from device using the following approaches. Check how-to-find-crash-logs or get-crash-reports-logs-from-iphone-ipad. You can symbolicate the crash log to find out the root cause. Check this question here for more details on that part Symbolicating iPhone App Crash Reports. Once you got the issue, you should be able to fix it.
Try this, put a temporary label then modify it when the didRecieveMemoryWarning is called or make an alert view that pops up when didRecieveMemoryWarning is called.
Also, run with Instruments app, its a great way to monitor your memory usage and identify memory leaks. Also try Product -> Analyze to find memory leaks from in-Xcode. Instruments is part of the SDK just search for it in spotlight.
I have both provisioned devices set up to be built to by XCode and the built-in iOS simulator. In general I like to do quick bug-fixes and early-stage testing in the simulator because it tends to be able to do multiple runs more quickly.
Does anyone know of a resource that lists known issues with the simulator? By "known issues" I mean situations where the simulator's behavior deviates significantly from that of the device. Sometimes I won't know if something is a genuine bug or just a simulator problem and it's kind of a pain to run on a testing device just to verify.
I just started doing some research into Core Location and it seems that the tutorials that I am following are not working for me. Even when I download the source code and run it, nothing happens. At present I have attempted this tutorial. When I run it, I get a popup asking if I want iPhone to use my current location. I press ok, and then nothing happens. Am I supposed to do anything else?
I am also using VMWare, and currently am unsure if this is the cause (although my internet connection works perfectly on it). I'm using base sdk ios 4.3 - running simulator.
In order for location to work, you need to be running the code on an actual device. The latest public iOS SDKs don't yet support location changes in the simulator. The simulator will always return 1 Infinite Loop, Cupertino, CA (Apple's headquarters) as the location.
See the Core Location documentation for more information on using location in your apps. (Although I can't find a citation for the limitation of the simulator at the moment.)
CoreLocation within the simulator is always going to return 1, Infinite Loop, Cupertino, CA, although Xcode 4.1 and iOS 5 have improved support for testing CoreLocation capabilities in the simulator.
iOS5 iPhone simulator supports location simulation.
If you are using 4.3, it does support location in some conditions. I notice that when I am tethering using my iPhone, my iPhone simulator is able to get location from my phone. I can see location update in my simulator when I'm working while commuting in a train. But this update is only through core location. Map gives u Cupertino unless u use iOS5