I recently migrated to using the M1 chip, I was using Intel before now. I wrote some test cases, that worked perfectly in the previous Intel MacBook. I wanted to run the same on M1 chips, but to my surprise, it always returns a blank white screen for all testcases. Has anyone experienced this? How was it resolved? Similar issues occur on 14 and higher. It would either show a white screen or display the app's onboarding UI and get stuck on it.
Related
I recently got a new macbook pro (2020 13-inch, running Big Sur v 11.1) and am using Rstudio (V 1.3.1093 with R version 4.0.3).
On my old computer, I often used the quartz() function to view my plots in the external graphics viewer. On my old mac, this would allow me to dynamically resize, keep fonts consistent, save directly from the resized version, etc. Now, on my new computer, it is behaving... strangely.
For example, when I run quartz() and a window opens, then I run a ggplot, the quartz window remains completely blank until I resize it just a tiny bit, then my plot appears. Even after the plot appears, sometimes the corners are cut off until I resize again, which then (I guess) refreshes the plot so it properly fills the space. The behavior with ggsave seems off, too, like the plots aren't saving exactly how they are appearing, which is the whole point of using the device.
Is anyone else having similar problems? I don't understand in great detail how graphics devices work, so I know this post is maybe not incredibly informative.
Thanks.
Can someone tell me if we can simulate 3DTouch with the Xcode 8 iOS simulator and how?
The option in my simulator looks like disable.
You need a Force Touch-enabled device, so either a Macbook with Force Touch-enabled trackpad, or any(?) Mac with a Magic Trackpad 2.
Did not tried it myself, but positive feedback here :
I can confirm that with Xcode 7.3 beta 5 (7D162j), I see a menu item in the Simulator for "Use Trackpad Force for 3D Touch." And when I connect my Magic Trackpad 2 to my '14 MacBook Air, that menu item becomes enabled and I can access peek & pop, shortcuts, and pretty much everything else. It's not a perfect simulation of 3D Touch (after all, they're based on different user-interaction paradigms), and there's a bit of lag, but it should be more than sufficient to test on the simulator.
From: https://forums.developer.apple.com/thread/26744
On an actual apple watch you can change the system font size, just like you can on the iPhone itself.
In doing so it's hi lighted a bug with what I was doing trying to get a timer interface object displaying at a smaller than standard size. I'm trying to test this on the simulator though and unfortunately you cannot seem to access the system text size on there. The apple watch app on the iPhone in the simulator doesn't show anything, and the apple watch simulator itself obviously just shows a black screen when not showing your app.
Is this just something that you cannot test on the simulator at the moment?
Cheers
There are many things that don't work in the simulator (yet). For example speech input, correct synchronization of NSUserDefaults, etc. You may file a bug report for your problem.
I'm working on a two months old project that was working till today, without any changes except maybe XCode update from 4.4 to 4.5.
I use RHAddressBook to read contacts groups, which seems to be a very good framework, but got a weird behavior.
In this order :
Simulating in iOS5 iPhone non retina : app displays a black screen, weird log :
objc[31712]: Class _NSZombie_CFCalendar is implemented in both ?? and ??. One of the two will be used. Which one is undefined.
Simulating in iOS6 iPhone non retina : everything works fine, groups are loaded and displayed, no log
Simulating in iOS5 iPhone non retina : app displays contact list but their seems to be a broken glass effect on the simulator display, and neither top or bottom bars are displayed, weird log again
Here is my storyboard (root view in navigation controller) :
And simulator screenshot for the same screen :
And the second screen (simple segue opening blank page) :
If some idea crosses your mind I'd be glad to hear it !
Thanks a lot.
EDIT: seems like this is an iPhone Simulator bug, I will try reinstalling it. On another app (SYGalleryExample from SYGallery) it displays it as if it was on an iPad, with the same broken glass effect, and here is another app perfectly working on production use :
EDIT 2: Reinstalling XCode, wiping out ~/Library/Developer and ~/Library/Application Support/iPhone Simulator folders didn't do anything. Seems like I'm going for a full system installation again.
EDIT 3: even iphone simulator "native" apps are active weird. Here is proof :
Everything fixed, Apple bug somewhere in my user files for iPhone Simulator on iOS5. To recap : the display of every app I built was screwed up, including app that were working yesterday without any change done till then.
Then I spotted also native apps were not OK, design was the iPad one on the simulated iPhone non retina device .
Logging in another session, launching the same native apps (settings, maps, etc) everything was fine.
Logged back on the original session, everything works again.
Hope this can help some future reader.
EDIT :
actually no, still not working. complete new install of osx on new hard drive, no time machine restore or whatsoever, run working project on ipad 5.0 simulator and still :
For me it only reproduced on iOS5, iOS6 worked fine.
This is how i managed to fix it:
The problem was that i had installed SwitchResX, which is a program that creates display profiles for mac. This application interfered with the resolution of the iPad simulator.
So my suggestion is to remove any applications that change your resolution or try a different display resolution.
How can you simulate a retina display (HiDPI mode) in Mac OS X 10.8 Mountain Lion on a non-retina display?
Search for, download, and install Apple's free Additional Tools for Xcode 8 (for previous Xcode releases search for Graphics Tools for Xcode according to your version).
Note: free Apple Developer account required.
Launch Quartz Debug application.
Go to menu: Window ---> UI Resolution.
Check Enable HiDPI display modes.
Quit Quartz Debug.
Open System Preferences.
Select Displays icon.
If using multiple display, select the configuration window on the display you wish to simulate HiDPI mode on.
Under Resolution:, select Scaled radio button.
Find a desired resolution postfixed with (HiDPI) and select it.
Your display is now running in HiDPI mode, simulating a retina display.
Source: High Resolution Guidelines for OS X
I found the following instructions. It seems to work, and it is much easier than the Quartz Debug approach.
"Enable HiDPI mode in Mountain Lion w/o Quartz Debug"
https://gist.github.com/3191869
In brief, run the following commands, log out, log on, and the HiDPI resolutions are available in the display preferences:
sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES
sudo defaults delete /Library/Preferences/com.apple.windowserver DisplayResolutionDisabled
(In my case the first command was enough; the second command just prints an error message.)
Edit: (5/31/2016)
For users trying to do this on El Capitan, please read the FAQ on SwitchRes's website. Also, if something's still not working after you did all the steps in the FAQ, consider uninstalling and reinstalling SwitchResX. That solved the issue I was having on one of my laptops.
Original:
After reading through several forums, websites, blogs.
I am here to present a solution for users with 15" MacBook Pro with Retina display connected to a Thunderbolt Display.
First of all,
Terminal command of modifying plist
Quartz Debug
Holding option and select "Scaled" in System Preferences
ResolutionTab (Mac App Store)
These methods DO NOT work for MBPr with Thunderbolt Display, for whatever reasons.
You will not see the HiDPI options to be selected.
The only tool I found that actually gives us the options is SwitchResX.
However another problem exists here.
Most users with this setup, I believe, are trying to use 1280x720 HiDPI because it's half the native resolution of the TBD.
According SwitchResX's FAQ, in some cases it is not possible to set to this resolution because of a bug within OS X itself.
Here's a screenshot for your reference:
After contacting the developer, he presented a workaround - adding one more pixel - which worked for me.
Install SwitchResX and open it from System Preferences.
Go to Thunderbolt Display tab, and add a Custom Resolutions with Scaled Resolution at 2562 x 1440
Here's a screenshot
Save using command + s. (or simply close the window and use the prompt up)
Restart the laptop.
Go to SwitchResX and select the new custom resolution in the Current Resolution tab. (Sometimes it doesn't show up right away, play around with it and it should.)
Here you go.
I hope this answer gets to users with this setup because it is really frustrating to use 16:10 resolution on a 16:9 display.
For those unable to enable HIDPI on rMBP or new MBA, I experienced the same on my rMBP 15" with Air Display. I solved the problem by installing SwitchResX. With the boolean setting enabled as shown in the referenced gist, the HIDPI setting shows up.
Dragging seems a little laggy in Air Display, but otherwise works great.
Try this
sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES
[from here]
If your monitor supports it, it may also be worth setting the DisplayPort version to 1.1 instead of 1.2.
I have a late 2010 Mac Air with a Samsung S27D850 display and had all sorts of intermittent resolution switching issues until I made that change.
As for me its pretty good app that give you opportunity for changing resolution any that you want.
SwitchResX for Mac and MacBook.
This app resolved all my problems with resolution.