Date   

Re: Puzzle with Hardened Runtime entitlement

Graham Cox
 


I misspoke - I’m not using Sparkle. I’m using Devmate - I thought that used Sparkle internally, but I’m not sure.

Anyway my other app that uses Devmate notarizes with no issues.

I cannot see any difference in the two targets.

—Graham




On 1 Nov 2019, at 2:19 pm, Jon Gotow <gotow@...> wrote:

On Oct 31, 2019, at 9:15 PM, Graham Cox <graham@...> wrote:

Yes, I have Sparkle and some 3rd party frameworks. I’ve checked the box that permits these to be loaded even though they’re signed by another developer.

Yes, have you turned on hardened runtime for the AutoUpdate app?





Re: Puzzle with Hardened Runtime entitlement

Graham Cox
 



On 1 Nov 2019, at 2:19 pm, Jack Brindle via Groups.Io <jackbrindle@...> wrote:

Have you checked the Notarization report? That will tell you exactly why it failed.


Yes ,this is what it says, which is what I said in my original message here

2019-11-01 03:54:51 +0000  Distribution items ineligible: Error Domain=IDEDistributionMethodDeveloperIDErrorDomain Code=1 "Hardened Runtime is not enabled." UserInfo={NSLocalizedDescription=Hardened Runtime is not enabled., NSLocalizedRecoverySuggestion="Ortelius 2.app" must be rebuilt with support for the Hardened Runtime. Enable the Hardened Runtime capability in the project editor, test your app, rebuild your archive, and upload again.}


Except, as far as I can tell, the Hardened Runtime is enabled.

—Graham




Re: Puzzle with Hardened Runtime entitlement

Jack Brindle
 

Have you checked the Notarization report? That will tell you exactly why it failed.

Jack

On Oct 31, 2019, at 8:15 PM, Graham Cox <graham@mapdiva.com> wrote:

Yes, I have Sparkle and some 3rd party frameworks. I’ve checked the box that permits these to be loaded even though they’re signed by another developer.

I have another app with much the same source code, settings and embedded frameworks. I was able to get that one notarized, even using the Xcode built-in tool. There’s somethng different about this one, but I can’t tell what it is.


—Graham



On 1 Nov 2019, at 12:34 pm, Jon Gotow <gotow@stclairsoft.com> wrote:

Have you got any helper applications (including those embedded in Sparkle or other frameworks)? Chances are it's actually complaining about one of those.

- Jon

On Oct 31, 2019, at 7:25 PM, Graham Cox <graham@mapdiva.com> wrote:

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:

<Screen Shot 2019-11-01 at 12.21.49 pm.png>


I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


—Graham







Re: Puzzle with Hardened Runtime entitlement

Jon Gotow
 

On Oct 31, 2019, at 9:15 PM, Graham Cox <graham@...> wrote:

Yes, I have Sparkle and some 3rd party frameworks. I’ve checked the box that permits these to be loaded even though they’re signed by another developer.

Yes, have you turned on hardened runtime for the AutoUpdate app?


I have another app with much the same source code, settings and embedded frameworks. I was able to get that one notarized, even using the Xcode built-in tool. There’s somethng different about this one, but I can’t tell what it is.

Are you building Sparkle from source within the app project, or building it as a separate framework? What's different between the two apps' projects?

 - Jon



Re: Puzzle with Hardened Runtime entitlement

Graham Cox
 

Yes, I have Sparkle and some 3rd party frameworks. I’ve checked the box that permits these to be loaded even though they’re signed by another developer.

I have another app with much the same source code, settings and embedded frameworks. I was able to get that one notarized, even using the Xcode built-in tool. There’s somethng different about this one, but I can’t tell what it is.


—Graham

On 1 Nov 2019, at 12:34 pm, Jon Gotow <gotow@stclairsoft.com> wrote:

Have you got any helper applications (including those embedded in Sparkle or other frameworks)? Chances are it's actually complaining about one of those.

- Jon

On Oct 31, 2019, at 7:25 PM, Graham Cox <graham@mapdiva.com> wrote:

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:

<Screen Shot 2019-11-01 at 12.21.49 pm.png>


I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


—Graham





Re: Puzzle with Hardened Runtime entitlement

Jon Gotow
 

Have you got any helper applications (including those embedded in Sparkle or other frameworks)? Chances are it's actually complaining about one of those.

- Jon

On Oct 31, 2019, at 7:25 PM, Graham Cox <graham@mapdiva.com> wrote:

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:

<Screen Shot 2019-11-01 at 12.21.49 pm.png>


I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


—Graham



Re: Puzzle with Hardened Runtime entitlement

Jack Brindle
 

Hardened Runtime is not currently a requirement for Notarization, but it appears that you have to submit the app using the command-line tool for notarization to happen properly. All my attempts at submitting using the Xcode archive method forces me to enable hardened runtime. I have not attempted at submission using Xcode 11, but when submitting with Xcode 10, I have had no problems with hardened runtime so far.

By the way, it appears that hardened runtime causes issues within Apple’s frameworks related to input monitoring. With it, we were not able to get the input monitoring prompt to appear. Removing it allowed our apps to operate properly. These apps do extensive work with BLE keyboard control.

So, you might want to use the command line method for submission to get around this, at least until the requirements change in January.

Jack


On Oct 31, 2019, at 6:25 PM, Graham Cox <graham@...> wrote:

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:

<Screen Shot 2019-11-01 at 12.21.49 pm.png>


I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


—Graham




Puzzle with Hardened Runtime entitlement

Graham Cox
 

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:



I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


—Graham



Re: Developer

Alex Zavatone
 

Then check the certificates and profiles in the signed package(s).  

I use a cery and profile inspector that someone wrote for Spotlight and is on Github.  




On Oct 17, 2019, at 11:42 PM, Carl Hoefs <newslists@...> wrote:

In our case, these apps are just for internal development purposes, such as student projects and the like. It's nice to be able to showcase them each semester, but the iPad apps always expire, and they have to be reinstalled onto the iPad from Xcode over and over again. All are using the same developer profile and certificate for all devices. Odd it would have an issue with just the iPad Pros? If I wipe/zero/reset the iPads clean and start over anew, might it clear this?

-Carl



On Oct 17, 2019, at 9:32 PM, Alex Zavatone via Groups.Io <zav@...> wrote:

There are some signing options where if you are part of a TestFlight team, your install will last for a certain time.  There are other install options where if you have an Enterprise cert installed (or something like that), the installation lasts longer.  I’d check which certs and mobileconfigs are installed on each device.  Also if one device is signed in to purchase the app from the App Store or to use TestFlight.

AZ


On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@...> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@...> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.














Re: Developer

Alexander von Below
 

Maybe this helps: Code to decode mobileprovisions https://github.com/below/cgjprofile

Von meinem iPhone gesendet

Am 19.10.2019 um 08:43 schrieb Gerriet M. Denkmann <gerriet@...>:



On 18 Oct 2019, at 06:26, Carl Hoefs <newslists@...> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@...> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Find …/Your iOS.app/embedded.mobileprovision, open in some editor and delete the first 62 bytes, so that it starts with:
“<?xml version="1.0" encoding="UTF-8”?>”
Save as: /anyPath/anyName.plist and open this in Xcode.

Look at ProvisionedDevices and TimeToLive.

It seems that every Developer Team has a List of (up to 100) ProvisionedDevices, which will build with TimeToLive = 365.
Building for a device which is *not* in ProvisionedDevices will get TimeToLive = 7.

So the problem reduces to: How to add a device to the list of ProvisionedDevices.
And I do not know the answer.
My Xcode seems to add any new device to this list by some kind of magic.

The Xcode of your boss (and of my poor friend) seems not to do this.


Gerriet.





Re: Developer

Bernie Maier
 

On Sat, 19 Oct 2019, at 5:42 PM, Gerriet M. Denkmann wrote:


Find …/Your iOS.app/embedded.mobileprovision, open in some editor and
delete the first 62 bytes, so that it starts with:
“<?xml version="1.0" encoding="UTF-8”?>”
Save as: /anyPath/anyName.plist and open this in Xcode.
Alternatively, run this on the command line to strip the security message container and signing from the contained plist:

```
security cms -D -i path-to.mobileprovision
```

I did some research into this a while ago (by I which I mean I did some searching and found other people’s research into this). I collected this and other related info into a public BitBucket snippet:

https://bitbucket.org/snippets/blurkk/5LB5LM

Cheers,
Bernie


Re: Developer

Gerriet M. Denkmann
 

On 18 Oct 2019, at 06:26, Carl Hoefs <newslists@autonomy.caltech.edu> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@mdenkmann.de> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?
Find …/Your iOS.app/embedded.mobileprovision, open in some editor and delete the first 62 bytes, so that it starts with:
“<?xml version="1.0" encoding="UTF-8”?>”
Save as: /anyPath/anyName.plist and open this in Xcode.

Look at ProvisionedDevices and TimeToLive.

It seems that every Developer Team has a List of (up to 100) ProvisionedDevices, which will build with TimeToLive = 365.
Building for a device which is *not* in ProvisionedDevices will get TimeToLive = 7.

So the problem reduces to: How to add a device to the list of ProvisionedDevices.
And I do not know the answer.
My Xcode seems to add any new device to this list by some kind of magic.

The Xcode of your boss (and of my poor friend) seems not to do this.


Gerriet.


Re: Developer

Carl Hoefs
 

In our case, these apps are just for internal development purposes, such as student projects and the like. It's nice to be able to showcase them each semester, but the iPad apps always expire, and they have to be reinstalled onto the iPad from Xcode over and over again. All are using the same developer profile and certificate for all devices. Odd it would have an issue with just the iPad Pros? If I wipe/zero/reset the iPads clean and start over anew, might it clear this?

-Carl



On Oct 17, 2019, at 9:32 PM, Alex Zavatone via Groups.Io <zav@...> wrote:

There are some signing options where if you are part of a TestFlight team, your install will last for a certain time.  There are other install options where if you have an Enterprise cert installed (or something like that), the installation lasts longer.  I’d check which certs and mobileconfigs are installed on each device.  Also if one device is signed in to purchase the app from the App Store or to use TestFlight.

AZ


On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@...> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@...> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.













Re: Developer

Alex Zavatone
 

There are some signing options where if you are part of a TestFlight team, your install will last for a certain time. There are other install options where if you have an Enterprise cert installed (or something like that), the installation lasts longer. I’d check which certs and mobileconfigs are installed on each device. Also if one device is signed in to purchase the app from the App Store or to use TestFlight.

AZ

On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@autonomy.caltech.edu> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@mdenkmann.de> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.







Re: Developer

Alex Zavatone
 

Seems like it’s a custom signed IPA.

On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@autonomy.caltech.edu> wrote:

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl


On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@mdenkmann.de> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.







Re: Developer

Carl Hoefs
 

Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.

-Carl

On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@mdenkmann.de> wrote:

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.





Re: NSScrollView showing part of view with white space above

Graham Cox
 

One thing I find when working with scroll views is that making the contained view flipped is usually helpful. If you return YES from an override to -isFlipped, scroll views default to a position with the the scroller at the top, not the bottom. It generally makes layout and calculations in the view easier as you are working with a more conventional coordinate system. Flipping the view generally doesn’t make anything else more difficult -in fact, usually easier.

Also, just set the bounds to whatever size you need and NSScrollView will generally just figure out everything else. You don’t need to directly manipulate the scrollbars or calculate anything.

—Graham



On 14 Oct 2019, at 12:30 am, Aandi Inston via Cocoa-dev <cocoa-dev@...> wrote:

But, the vertical scroll bar position is at the BOTTOM of the window. 


UITableView selection changed at some point

Steve Mills
 

I have a UITableView that has x number of simple rows (name and image), then one row at the end that also has a name and image, but also uses a disclosure indicator accessory, which opens a new scene (I'll call it scene B) when tapped. In previous versions of iOS (currently I can only check 10.0), tapping that last row would select it, and then when returning from the scene B, it would still correctly be selected. Now in iOS 13, it no longer *appears* to be selected when I return from scene B. But, if I get the table view's indexPathForSelectedRow, it is indeed the correct row.

Is there something I need to do to fix this? I'll obviously report this bug, but I sure would like to find a hack to make it work correctly.

--
Steve Mills
Drummer, Mac geek


Developer

Gerriet M. Denkmann
 

A friend of mine has a problem:

When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year).
But when he installs the same app on his iPad, the app will expire after just one week.

What could be the reason for this behaviour?

Gerriet.


Re: CMSensorRecorder.accelerometerDataSince(_:) missing?

Fritz Anderson
 

I found one reference for iOS 10:


but on inspection it’s clear it’s derived from a class dump, not the documented interface. Hence accursed for distribution.

Off to Feedback Assistant to ask that the API be exposed.

— F

On 25 Sep 2019, at 7:50 PM, Quincey Morris <quinceymorris@...> wrote:

On Sep 25, 2019, at 14:49 , Fritz Anderson <anderson.fritz@...> wrote:

Xcode 11 won’t complete the symbol; it raises an error when I try to use it anyway; and the derived interface for the class doesn’t include it.

It’s not in the Obj-C header file either. (iOS 13.0 SDK in Xcode 11) This just looks like an error in the documentation.

Perhaps this method existed for a while in the beta period for 13.0. I checked in the iOS 13.1 SDK (Xcode 11.1 beta), but it’s also not there.

361 - 380 of 1420