Date   

Debugging the view hierarchy on an iOS launch screen storyboard.

Alex Zavatone
 

Hi everyone. I’ve got an interesting issue where one graphic disappears on a launch screen, but only on some iOS devices.

My first tendency is to use the View Hierarchy Debugger, but if I set a breakpoint on main(), there’s nothing displayed in the View Hierarchy Debugger.

How would I go about getting the view hierarchy of the launch screen storyboard and hopefully seeing it in the View Hierarchy Debugger?

Thanks in advance,

Alex Zavatone


Re: Big Sur Terminal editing weirdness

Alex Zavatone
 

Glad that they have good QA.

On Apr 30, 2021, at 12:20 PM, dhoerl via groups.io <dhoerl=mac.com@groups.io> wrote:

I ues "vi" mode in my shell to edit command lines - but since I updated to Big Sur (or was it an M1?), sometimes when I'd edit a line the cursor would go back a line.

Took me forever to track it down, but Terminal (at least for me) is not setting "COLUMNS", so it defaults to 80.

In previous releases, the shell would get the set and updated as Terminal windows resized.

Posting this in case someone else has the same puzzling issues.

BTW my fix was to just set COLUMNS to 512 in my profile. But really...






Big Sur Terminal editing weirdness

dhoerl
 

I ues "vi" mode in my shell to edit command lines - but since I updated to Big Sur (or was it an M1?), sometimes when I'd edit a line the cursor would go back a line.

Took me forever to track it down, but Terminal (at least for me) is not setting "COLUMNS", so it defaults to 80.

In previous releases, the shell would get the set and updated as Terminal windows resized.

Posting this in case someone else has the same puzzling issues.

BTW my fix was to just set COLUMNS to 512 in my profile. But really...


Re: iOS "This app cannot be installed because its integrity could not be verified"

Alex Zavatone
 

Nothing that brand new provisioning profiles couldn’t fix.

On Apr 29, 2021, at 12:50 PM, Alex Zavatone via groups.io <zav@...> wrote:

Wondering if anyone has run into this recently on iOS.  

I made a 1 screen simple iOS app to test uploading to an internal app store for a client and that’s working fine.  When the client clicks to install the app on iOS, she gets 

“Unable to Install” 
“This app cannot be installed because its integrity could not be verified”

It looks like lots of other people have been running across this as of iOS 14.2 but I haven’t come across a clear explanation what the cause of this is.

Any insight into a possible cause?

Best,
Alex Zavatone


iOS "This app cannot be installed because its integrity could not be verified"

Alex Zavatone
 

Wondering if anyone has run into this recently on iOS.  

I made a 1 screen simple iOS app to test uploading to an internal app store for a client and that’s working fine.  When the client clicks to install the app on iOS, she gets 

“Unable to Install” 
“This app cannot be installed because its integrity could not be verified”

It looks like lots of other people have been running across this as of iOS 14.2 but I haven’t come across a clear explanation what the cause of this is.

Any insight into a possible cause?

Best,
Alex Zavatone


Re: Question about Xcode 12.5 Clang compiler release notes.

Jack Brindle
 

Oops. Sorry. new and alloc are +, but init is definitely -. You are right +init is an error.
So, file a bug report? ;-)

Jack

On Apr 27, 2021, at 7:27 AM, Jack Brindle via groups.io <jackbrindle@...> wrote:

No. It is correct. Both new and alloc are + methods since they act on the class, and not an object. If you think about it, there is no object to message when you use them.
From the docs:
+ (instancetype)new;

This method is a combination of alloc and init. Like alloc, it initializes the isa instance variable of the new object so it points to the class data structure. It then invokes the init method to complete the initialization process.

Jack


On Apr 27, 2021, at 6:42 AM, Alex Zavatone via groups.io <zav@...> wrote:

From the release notes


> Clang now infers the availability of 
+new from availability annotations on -init methods. 
>
> Since +new calls [[Foo alloc] init]+new isn’t available unless +init is available. (75884815)


+init?  Is this a typo in the release notes??

Thanks in advance.
Alex Zavatone



Re: Question about Xcode 12.5 Clang compiler release notes.

Jack Brindle
 

No. It is correct. Both new and alloc are + methods since they act on the class, and not an object. If you think about it, there is no object to message when you use them.
From the docs:
+ (instancetype)new;

This method is a combination of alloc and init. Like alloc, it initializes the isa instance variable of the new object so it points to the class data structure. It then invokes the init method to complete the initialization process.

Jack


On Apr 27, 2021, at 6:42 AM, Alex Zavatone via groups.io <zav@...> wrote:

From the release notes


> Clang now infers the availability of 
+new from availability annotations on -init methods. 
>
> Since +new calls [[Foo alloc] init]+new isn’t available unless +init is available. (75884815)


+init?  Is this a typo in the release notes??

Thanks in advance.
Alex Zavatone


Question about Xcode 12.5 Clang compiler release notes.

Alex Zavatone
 

From the release notes


> Clang now infers the availability of 
+new from availability annotations on -init methods. 
>
> Since +new calls [[Foo alloc] init]+new isn’t available unless +init is available. (75884815)


+init?  Is this a typo in the release notes??

Thanks in advance.
Alex Zavatone


measuring Metal FPS

James Walker
 

When running a macOS app rendering with Metal under the Xcode 12 debugger, the debug navigator displays FPS (frame rate) among other things. But if I launch the program outside Xcode and attach to the process, the debug navigator does not show FPS, though it does show memory usage and such. What's up with that? I tried changing the Run mode of the scheme to use the Release build instead of the the Debug build, but then rendering was quite noticeably slower. Is there some quick way to get a frame rate? I'm aware that Instruments can measure various things relating to Metal, but it's not obvious to me how to see something as simple as a frame rate.


Re: Freshly made Apple Developer and Distribution certs certs not trusted.

Alex Zavatone
 

Well, how interesting.

Installing the AWWDRCA cert from here enabled my freshly created certs even though I already had a valid AWWDRCA cert installed.


Even though I had a valid AWWDRCA cert installed in the keychain, it wasn’t good enough.  I now have 3 valid ones.


Note that one expires on Feb 7, 2023 and the other expires on Feb 19, 2030.

I hope this is useful to others.

Cheers,
Alex Zavatone


On Mar 17, 2021, at 1:17 PM, Alex Zavatone via groups.io <zav@...> wrote:

Has anyone run in to this?  I just made brand new “Apple” distro and dev certs and both appear to be not trusted because “no root certificate found”.

The issuer name is Apple Worldwide Developer Relations Certification Authority.

Checking out my installed certs now and the Apple WWDC cert.

Thanks.
Alex Zavatone






Freshly made Apple Developer and Distribution certs certs not trusted.

Alex Zavatone
 

Has anyone run in to this? I just made brand new “Apple” distro and dev certs and both appear to be not trusted because “no root certificate found”.

The issuer name is Apple Worldwide Developer Relations Certification Authority.

Checking out my installed certs now and the Apple WWDC cert.

Thanks.
Alex Zavatone


Re: Provisioning Profile Manager

Jack Brindle
 

Alex;

Thanks for the info. With Provisioning Profiles starting to be important for Mac development, utilities of this sort are becoming useful for us Mac types as well.

Jack

On Feb 26, 2021, at 11:02 AM, Alex Zavatone via groups.io <zav=mac.com@groups.io> wrote:

I’m not sure where I came across this, but remembering a discussion we had about either certs or provisioning profiles, I thought I’d share this tool with the group.

Provisioning Profile Manager

https://apps.apple.com/us/app/provisioning-profile-manager/id1386246293?mt=12

One reason why tools like these matter is in at least one of Xcode’s processes where it uses certs or profiles will fail if one of your certs is expired. I think this is in build validation with the App Store on iOS. From what I remember from 2015 is that if you have a valid cert backing your provisioning profile(s) and you also have one expired one in your keychain, it’s the invalid one that invalidates an IPA verification with the App Store for upload.

Cheers,
Alex Zavatone




Provisioning Profile Manager

Alex Zavatone
 

I’m not sure where I came across this, but remembering a discussion we had about either certs or provisioning profiles, I thought I’d share this tool with the group.

Provisioning Profile Manager

https://apps.apple.com/us/app/provisioning-profile-manager/id1386246293?mt=12

One reason why tools like these matter is in at least one of Xcode’s processes where it uses certs or profiles will fail if one of your certs is expired. I think this is in build validation with the App Store on iOS. From what I remember from 2015 is that if you have a valid cert backing your provisioning profile(s) and you also have one expired one in your keychain, it’s the invalid one that invalidates an IPA verification with the App Store for upload.

Cheers,
Alex Zavatone


Re: Problem with IB in Xcode 12.4

Sak Wathanasin
 



On 24 Feb 2021, at 01:13, Jack Brindle via groups.io <jackbrindle@...> wrote:

On the top left side of the middle section of the Xcode window there is an icon that consists of four squares. Click on it and you will find the counterparts item you seek, along with quite a few other things (like “Recent Files”, “Changed Files” and some more actually useful items.


Thanks for that & to Dave for pointing out that the commands are still there under "Navigation". I'm having to use the "4-squares" (what do you call it?)  menu, but my fingers are conditioned to hit that key-combo and it's disconcerting to say the least when an unexpected file appears.

Update: A little more experimentation shows that if I have foo.m, foo.h and footest.m, that key combo cycles between them. So I guess it's a "feature".

And the control-drag in IB now works for me, so I must have been having an off day.

Sorry for the waste of bandwaidth!

Sak


Re: Problem with IB in Xcode 12.4

Jack Brindle
 

On the top left side of the middle section of the Xcode window there is an icon that consists of four squares. Click on it and you will find the counterparts item you seek, along with quite a few other things (like “Recent Files”, “Changed Files” and some more actually useful items.

I think Apple moves things around just to do it.

Jack

On Feb 23, 2021, at 2:38 PM, Sak Wathanasin <sw@network-analysis.ltd.uk> wrote:

In XC 12.4, control-dragging from a widget in an XIB to a .m file to create an action or to a .h to create an outlet no lnger seems to work. It pops up some error. Works in 12.3 though. Did I imagine it or has someone already posted about it here? If not, I'll raise a bug report.

Also, control-command-up -arrow (or down-arrow) to switch between .m & .h files no longer works (even in 12.3). Instead it tries to open a matching unit test file. I guess this may be for the convenience of Swifties, but some of us still have to work with ObjC files. Since this key-combo doesn't appear in the key-shortcuts ("Open Counterpart" having been removed from the File menu ages ago), any ideas as to how I can get the old behaviour back? My fingers are conditioned to use this key-combo.

Thanks
Sak






Re: Problem with IB in Xcode 12.4

davelist@...
 

On Feb 23, 2021, at 5:38 PM, Sak Wathanasin <sw@network-analysis.ltd.uk> wrote:

In XC 12.4, control-dragging from a widget in an XIB to a .m file to create an action or to a .h to create an outlet no lnger seems to work. It pops up some error. Works in 12.3 though. Did I imagine it or has someone already posted about it here? If not, I'll raise a bug report.

Also, control-command-up -arrow (or down-arrow) to switch between .m & .h files no longer works (even in 12.3). Instead it tries to open a matching unit test file. I guess this may be for the convenience of Swifties, but some of us still have to work with ObjC files. Since this key-combo doesn't appear in the key-shortcuts ("Open Counterpart" having been removed from the File menu ages ago), any ideas as to how I can get the old behaviour back? My fingers are conditioned to use this key-combo.

Thanks
Sak
I didn't check the first one, but for the second one, that still works for me with Objective-C. It's in the Navigate menu (not the File menu) - Jump to Previous Counterpart and Jump to Next Counterpart for control-command down and up arrow. Now the file I tested it with are just .h and .m (no matching unit test file with same prefix as file), but I'd try the menu options first to see what they do.

Dave


Re: Problem with IB in Xcode 12.4

Alex Zavatone
 

On Feb 23, 2021, at 4:38 PM, Sak Wathanasin <sw@network-analysis.ltd.uk> wrote:

In XC 12.4, control-dragging from a widget in an XIB to a .m file to create an action or to a .h to create an outlet no lnger seems to work. It pops up some error. Works in 12.3 though. Did I imagine it or has someone already posted about it here? If not, I'll raise a bug report.

Also, control-command-up -arrow (or down-arrow) to switch between .m & .h files no longer works (even in 12.3). Instead it tries to open a matching unit test file. I guess this may be for the convenience of Swifties, but some of us still have to work with ObjC files. Since this key-combo doesn't appear in the key-shortcuts ("Open Counterpart" having been removed from the File menu ages ago), any ideas as to how I can get the old behaviour back? My fingers are conditioned to use this key-combo.

Thanks
Sak
Does command control up or down work after a successful build? I’ve seen it being really flakey recently but haven’t bothered to try and narrow it down as to what causes it.


Problem with IB in Xcode 12.4

Sak Wathanasin
 

In XC 12.4, control-dragging from a widget in an XIB to a .m file to create an action or to a .h to create an outlet no lnger seems to work. It pops up some error. Works in 12.3 though. Did I imagine it or has someone already posted about it here? If not, I'll raise a bug report.

Also, control-command-up -arrow (or down-arrow) to switch between .m & .h files no longer works (even in 12.3). Instead it tries to open a matching unit test file. I guess this may be for the convenience of Swifties, but some of us still have to work with ObjC files. Since this key-combo doesn't appear in the key-shortcuts ("Open Counterpart" having been removed from the File menu ages ago), any ideas as to how I can get the old behaviour back? My fingers are conditioned to use this key-combo.

Thanks
Sak


Question about Push notification server new cert

Owen Hartnett
 

I’m running a push notification server for our app. It’s working fine. I came across this notice:

https://developer.apple.com/news/?id=7gx0a2lp

and I’m confused where these new certs go.

Previously, just had to generate a push cert through the developer portal and use that cert to send through Pushy (a java apns library) to connect to the server.

It sounds like there’s going to be an additional burden.

Does this mean:

a) I just have to regenerate a new cert through the developer portal and use that

b) I need to download the new certs, install them somewhere in my linux box which is our provider into APNS.

If b), do I install this like an apache certificate (I’m running apache), or does it go into some special linux place for certs

It’s unclear to me where this cert fits in, and where I need to place it.

FYI: I’m running a Certificate-based connection to APNs using a java webapp under Apache.

Any pointers you can give would be helpful.

Thanks!

-Owen


Re: Problems with exporting an archived app

Giacomo Tufano
 

About Xcode caches and various files, I can recommend DevCleaner (for free on the Mac Store, I’m not affiliated in any way, I’m just an happy user). It makes easier to remove files than manually look into ~/Library/Developer (and gives you an idea of how much space the actions will free)

Il giorno 11 feb 2021, alle ore 19:27, Alex Zavatone via groups.io <zav@...> ha scritto:


As an Xcode developer, our drives get filled up way too easily.  You can look in several places for several GB to recover.

For example, checking the ~/Library/Developer folder on this Mac shows that I’ve got 64 GB used in that folder.
33.23GB for the Xcode folder 
30.67GB for the CoreSimulator folder

Within the ~/Library/Develope/Xcode folder, the big eaters of space are in iOS DeviceSupport  from all OSes from 9.1 to 14.3 with 30 GB used.  Check yours and see what can be thinned out.

21 - 40 of 1397