Catalina mail recovery stack

[Neville via use-livecode]

After installing Catalina macOS I (along with lots of other people) lost a 
whole swag of mail; the problem seems to occur after moving a message between 
mailboxes, possibly before Mail had finished updating itself, but may have 
other triggers. Many messages simply went totally missing, and lots of message 
(in custom mailboxes) are shown with a header but no content. Remedies 
suggested in various fora haven’t worked: rebuilding mailboxes didn’t help, 
even with manual removal of the Mail.app Envelope databases, and Time Machine 
cannot be used at least in its in its simple mode to recover mail. With over 
85000 emails and the byzantine directory structure of the email messages, there 
is no way I can manually search for the missing email in the backups.

I am writing a stack to create a custom sqlite database of messages from the 
standard Mac ~/Library/Mail location, and from Time Machine backup locations, 
and include tools to compare and find emails. So far it seems to be successful 
in finding lost messages; I have yet to add tools to reimport to Mail.app.

If anyone has this lost mail problem (and has a Time Machine or other backup) 
and would like my stack please email me. The stack is rough for my own use at 
the moment but I can polish it for general use.

neville.smy...@optusnet.com .au
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Tester in iPhone 8 Not Getting Audio

[Sannyasin Brahmanathaswami via use-livecode]

FYI, I started using TestFlight in iOS and  have a broader group testing the 
app.

iPhone8 is no longer playing audio any time after iOS >12.

Upgrading to 13.2.2 doesn't fix it! Sad. I have to release the app… with a 
disclaimer for iPhone 8 users….


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: New app update: four errors in plist

[Sannyasin Brahmanathaswami via use-livecode]

FYI, you click "Beta Test" in standalone settings and you will get the "beta 
entitlement", properly installed , which is required if you want to use Test 
Flight.





In standalone settings I see three options: Required, Prohibited, n/a. 
Do you mean the plist always contains a location option even if "n/a" is 
selected? That doesn't seem right.

On 11/15/19 4:47 AM, William de Smet via use-livecode wrote:
Hi Jacqueline,
One of the two options is always selected.
You can't select none.
The 'problem' is that there is one required key missing now so you have to
add it yourself bij editing the plist.
After editing the plist the app update was approved within 6 hours #quick
greetings,
William
Op vr 15 nov. 2019 om 02:07 schreef J. Landman Gay via use-livecode <
mailto:use-livecode@lists.runrev.com>:
Is the location key included in the plist if you don't select location
services in standalone settings? (I haven't built for iOS in a long time.)

--
Jacqueline Landman Gay | mailto:jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 14, 2019 3:05:17 PM Ralph DiMola via use-livecode
 wrote:

ITMS-90339: from iOS 12(or 13?) an app automatically does NOT exit on
suspend. You need this key for legacy OS versions. You will not be
rejected
for this(yet).
ITMS-90078: will also not get you rejected. This is caused by some
library
binding issue that Mark explained a while back.
ITMS-90191: Also a warning. This is for Beta testing. You can enable the
beta entitlement when generating a provisioning profile.
ITMS-90683: This is the one that will get you rejected. For example if
you
use location services you will have to hack the IDE to change the text of
the location request text. This can be a pain because you have to do it
every time the IDE is started. What I do:
1) In the message box ==> "put the script of "revSaveAsIosStandalone"
into
url ("/somePath/someFilename")
2) Edit the text file(See QCC 22150)

After that every time you want to submit to the app store do this in the
message box ==> set the script of "revSaveAsIosStandalone" to url
("/somePath/someFilename")

Ralph DiMola
IT Director
Evergreen Information Services
mailto:rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
Behalf
Of William de Smet via use-livecode
Sent: Thursday, November 14, 2019 2:00 PM
To: How to use LiveCode
Cc: William de Smet
Subject: New app update: four errors in plist

Hi there,

Today I uploaded an update for one of my apps to the App Store.
Now I have four errors coming back from Apple.
Still need to edit the info.plist but it'd easy to make a mistake with
this.
When will this be fixed?

-
Got this notification back:
ITMS-90339: Deprecated Info.plist Key - The Info.plist contains a key
'UIApplicationExitsOnSuspend' in bundle shutthebox [shutthebox.app] that
will soon be unsupported. Remove the key, rebuild your app and resubmit.

ITMS-90078: Missing Push Notification Entitlement - Your app appears to
register with the Apple Push Notification service, but the app
signature's
entitlements do not include the "aps-environment" entitlement. If your
app
uses the Apple Push Notification service, make sure your App ID is
enabled
for Push Notification in the Provisioning Portal, and resubmit after
signing
your app with a Distribution provisioning profile that includes the
"aps-environment" entitlement. Xcode does not automatically copy the
aps-environment entitlement from provisioning profiles at build time.
This
behavior is intentional. To use this entitlement, either enable Push
Notifications in the project editor's Capabilities pane, or manually add
the
entitlement to your entitlements file. For more information, see

https://developer.apple.com/library/content/documentation/NetworkingInternet

/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_r
ef/doc/uid/TP40008194-CH6-SW1
.

ITMS-90191: Missing beta entitlement - Your app does not include the
beta-reports-active entitlement. If you intend to distribute this build
via
TestFlight for beta testing, please re-build this app with an App Store
Distribution provisioning profile. Do not use ad-hoc profiles.

ITMS-90683: Missing Purpose String in Info.plist - Your app's code
references one or more APIs that access sensitive user data. The app's
Info.plist file should contain a NSLocationAlwaysUsageDescription key
with a
user-facing purpose string explaining clearly and completely why your app
needs the data. Starting Spring 2019, all apps submitted to the App Store
that access user data are required to include a purpose string. If you're
using external libraries or SDKs, they may reference APIs that require a
purpose string. While your app might not use these APIs, a purpose
string is
still required. You can contact the developer of the library or SDK and
request they release a version of their code that doesn't contain the

Re: New app update: four errors in plist

[J. Landman Gay via use-livecode]

In standalone settings I see three options: Required, Prohibited, n/a. 
Do you mean the plist always contains a location option even if "n/a" is 
selected? That doesn't seem right.


On 11/15/19 4:47 AM, William de Smet via use-livecode wrote:

Hi Jacqueline,

One of the two options is always selected.
You can't select none.
The 'problem' is that there is one required key missing now so you have to
add it yourself bij editing the plist.

After editing the plist the app update was approved within 6 hours #quick


greetings,

William




Op vr 15 nov. 2019 om 02:07 schreef J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com>:


Is the location key included in the plist if you don't select location
services in standalone settings? (I haven't built for iOS in a long time.)

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 14, 2019 3:05:17 PM Ralph DiMola via use-livecode
 wrote:


ITMS-90339: from iOS 12(or 13?) an app automatically does NOT exit on
suspend. You need this key for legacy OS versions. You will not be

rejected

for this(yet).
ITMS-90078: will also not get you rejected. This is caused by some

library

binding issue that Mark explained a while back.
ITMS-90191: Also a warning. This is for Beta testing. You can enable the
beta entitlement when generating a provisioning profile.
ITMS-90683: This is the one that will get you rejected. For example if

you

use location services you will have to hack the IDE to change the text of
the location request text. This can be a pain because you have to do it
every time the IDE is started. What I do:
1) In the message box ==> "put the script of "revSaveAsIosStandalone"

into

url ("File://somePath/someFilename")
2) Edit the text file(See QCC 22150)

After that every time you want to submit to the app store do this in the
message box ==> set the script of "revSaveAsIosStandalone" to url
("File://somePath/someFilename")

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On

Behalf

Of William de Smet via use-livecode
Sent: Thursday, November 14, 2019 2:00 PM
To: How to use LiveCode
Cc: William de Smet
Subject: New app update: four errors in plist

Hi there,

Today I uploaded an update for one of my apps to the App Store.
Now I have four errors coming back from Apple.
Still need to edit the info.plist but it'd easy to make a mistake with

this.

When will this be fixed?

-
Got this notification back:
ITMS-90339: Deprecated Info.plist Key - The Info.plist contains a key
'UIApplicationExitsOnSuspend' in bundle shutthebox [shutthebox.app] that
will soon be unsupported. Remove the key, rebuild your app and resubmit.

ITMS-90078: Missing Push Notification Entitlement - Your app appears to
register with the Apple Push Notification service, but the app

signature's

entitlements do not include the "aps-environment" entitlement. If your

app

uses the Apple Push Notification service, make sure your App ID is

enabled

for Push Notification in the Provisioning Portal, and resubmit after

signing

your app with a Distribution provisioning profile that includes the
"aps-environment" entitlement. Xcode does not automatically copy the
aps-environment entitlement from provisioning profiles at build time.

This

behavior is intentional. To use this entitlement, either enable Push
Notifications in the project editor's Capabilities pane, or manually add

the

entitlement to your entitlements file. For more information, see


https://developer.apple.com/library/content/documentation/NetworkingInternet



/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_r

ef/doc/uid/TP40008194-CH6-SW1
.

ITMS-90191: Missing beta entitlement - Your app does not include the
beta-reports-active entitlement. If you intend to distribute this build

via

TestFlight for beta testing, please re-build this app with an App Store
Distribution provisioning profile. Do not use ad-hoc profiles.

ITMS-90683: Missing Purpose String in Info.plist - Your app's code
references one or more APIs that access sensitive user data. The app's
Info.plist file should contain a NSLocationAlwaysUsageDescription key

with a

user-facing purpose string explaining clearly and completely why your app
needs the data. Starting Spring 2019, all apps submitted to the App Store
that access user data are required to include a purpose string. If you're
using external libraries or SDKs, they may reference APIs that require a
purpose string. While your app might not use these APIs, a purpose

string is

still required. You can contact the developer of the library or SDK and
request they release a version of their code that doesn't contain the

APIs.

Learn more (


https://developer.apple.com/documentation/uikit/core_app/protecting_the_user

_s_privacy
).
-

Greetings,

William

Re: New app update: four errors in plist

[William de Smet via use-livecode]

Hi Ralph,

I used a custom plist and add it to the 'Copy files pane' of the standalone
settings.
Works fine but you need to focus :-)

After editing the plist the app update was approved within 6 hours
#quick


greetings,

William




Op do 14 nov. 2019 om 22:04 schreef Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com>:

> ITMS-90339: from iOS 12(or 13?) an app automatically does NOT exit on
> suspend. You need this key for legacy OS versions. You will not be rejected
> for this(yet).
> ITMS-90078: will also not get you rejected. This is caused by some library
> binding issue that Mark explained a while back.
> ITMS-90191: Also a warning. This is for Beta testing. You can enable the
> beta entitlement when generating a provisioning profile.
> ITMS-90683: This is the one that will get you rejected. For example if you
> use location services you will have to hack the IDE to change the text of
> the location request text. This can be a pain because you have to do it
> every time the IDE is started. What I do:
> 1) In the message box ==> "put the script of "revSaveAsIosStandalone" into
> url ("File://somePath/someFilename")
> 2) Edit the text file(See QCC 22150)
>
> After that every time you want to submit to the app store do this in the
> message box ==> set the script of "revSaveAsIosStandalone" to url
> ("File://somePath/someFilename")
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of William de Smet via use-livecode
> Sent: Thursday, November 14, 2019 2:00 PM
> To: How to use LiveCode
> Cc: William de Smet
> Subject: New app update: four errors in plist
>
> Hi there,
>
> Today I uploaded an update for one of my apps to the App Store.
> Now I have four errors coming back from Apple.
> Still need to edit the info.plist but it'd easy to make a mistake with
> this.
> When will this be fixed?
>
> -
> Got this notification back:
> ITMS-90339: Deprecated Info.plist Key - The Info.plist contains a key
> 'UIApplicationExitsOnSuspend' in bundle shutthebox [shutthebox.app] that
> will soon be unsupported. Remove the key, rebuild your app and resubmit.
>
> ITMS-90078: Missing Push Notification Entitlement - Your app appears to
> register with the Apple Push Notification service, but the app signature's
> entitlements do not include the "aps-environment" entitlement. If your app
> uses the Apple Push Notification service, make sure your App ID is enabled
> for Push Notification in the Provisioning Portal, and resubmit after
> signing
> your app with a Distribution provisioning profile that includes the
> "aps-environment" entitlement. Xcode does not automatically copy the
> aps-environment entitlement from provisioning profiles at build time. This
> behavior is intentional. To use this entitlement, either enable Push
> Notifications in the project editor's Capabilities pane, or manually add
> the
> entitlement to your entitlements file. For more information, see
>
> https://developer.apple.com/library/content/documentation/NetworkingInternet
>
> /Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_r
> ef/doc/uid/TP40008194-CH6-SW1
> 
> .
>
> ITMS-90191: Missing beta entitlement - Your app does not include the
> beta-reports-active entitlement. If you intend to distribute this build via
> TestFlight for beta testing, please re-build this app with an App Store
> Distribution provisioning profile. Do not use ad-hoc profiles.
>
> ITMS-90683: Missing Purpose String in Info.plist - Your app's code
> references one or more APIs that access sensitive user data. The app's
> Info.plist file should contain a NSLocationAlwaysUsageDescription key with
> a
> user-facing purpose string explaining clearly and completely why your app
> needs the data. Starting Spring 2019, all apps submitted to the App Store
> that access user data are required to include a purpose string. If you're
> using external libraries or SDKs, they may reference APIs that require a
> purpose string. While your app might not use these APIs, a purpose string
> is
> still required. You can contact the developer of the library or SDK and
> request they release a version of their code that doesn't contain the APIs.
> Learn more (
>
> https://developer.apple.com/documentation/uikit/core_app/protecting_the_user
> _s_privacy
> ).
> -
>
> Greetings,
>
> William
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> ___
> use-livecode 

Re: New app update: four errors in plist

[William de Smet via use-livecode]

Hi Jacqueline,

One of the two options is always selected.
You can't select none.
The 'problem' is that there is one required key missing now so you have to
add it yourself bij editing the plist.

After editing the plist the app update was approved within 6 hours #quick


greetings,

William




Op vr 15 nov. 2019 om 02:07 schreef J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com>:

> Is the location key included in the plist if you don't select location
> services in standalone settings? (I haven't built for iOS in a long time.)
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On November 14, 2019 3:05:17 PM Ralph DiMola via use-livecode
>  wrote:
>
> > ITMS-90339: from iOS 12(or 13?) an app automatically does NOT exit on
> > suspend. You need this key for legacy OS versions. You will not be
> rejected
> > for this(yet).
> > ITMS-90078: will also not get you rejected. This is caused by some
> library
> > binding issue that Mark explained a while back.
> > ITMS-90191: Also a warning. This is for Beta testing. You can enable the
> > beta entitlement when generating a provisioning profile.
> > ITMS-90683: This is the one that will get you rejected. For example if
> you
> > use location services you will have to hack the IDE to change the text of
> > the location request text. This can be a pain because you have to do it
> > every time the IDE is started. What I do:
> > 1) In the message box ==> "put the script of "revSaveAsIosStandalone"
> into
> > url ("File://somePath/someFilename")
> > 2) Edit the text file(See QCC 22150)
> >
> > After that every time you want to submit to the app store do this in the
> > message box ==> set the script of "revSaveAsIosStandalone" to url
> > ("File://somePath/someFilename")
> >
> > Ralph DiMola
> > IT Director
> > Evergreen Information Services
> > rdim...@evergreeninfo.net
> >
> > -Original Message-
> > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> > Of William de Smet via use-livecode
> > Sent: Thursday, November 14, 2019 2:00 PM
> > To: How to use LiveCode
> > Cc: William de Smet
> > Subject: New app update: four errors in plist
> >
> > Hi there,
> >
> > Today I uploaded an update for one of my apps to the App Store.
> > Now I have four errors coming back from Apple.
> > Still need to edit the info.plist but it'd easy to make a mistake with
> this.
> > When will this be fixed?
> >
> > -
> > Got this notification back:
> > ITMS-90339: Deprecated Info.plist Key - The Info.plist contains a key
> > 'UIApplicationExitsOnSuspend' in bundle shutthebox [shutthebox.app] that
> > will soon be unsupported. Remove the key, rebuild your app and resubmit.
> >
> > ITMS-90078: Missing Push Notification Entitlement - Your app appears to
> > register with the Apple Push Notification service, but the app
> signature's
> > entitlements do not include the "aps-environment" entitlement. If your
> app
> > uses the Apple Push Notification service, make sure your App ID is
> enabled
> > for Push Notification in the Provisioning Portal, and resubmit after
> signing
> > your app with a Distribution provisioning profile that includes the
> > "aps-environment" entitlement. Xcode does not automatically copy the
> > aps-environment entitlement from provisioning profiles at build time.
> This
> > behavior is intentional. To use this entitlement, either enable Push
> > Notifications in the project editor's Capabilities pane, or manually add
> the
> > entitlement to your entitlements file. For more information, see
> >
> https://developer.apple.com/library/content/documentation/NetworkingInternet
> >
> /Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_r
> > ef/doc/uid/TP40008194-CH6-SW1
> > .
> >
> > ITMS-90191: Missing beta entitlement - Your app does not include the
> > beta-reports-active entitlement. If you intend to distribute this build
> via
> > TestFlight for beta testing, please re-build this app with an App Store
> > Distribution provisioning profile. Do not use ad-hoc profiles.
> >
> > ITMS-90683: Missing Purpose String in Info.plist - Your app's code
> > references one or more APIs that access sensitive user data. The app's
> > Info.plist file should contain a NSLocationAlwaysUsageDescription key
> with a
> > user-facing purpose string explaining clearly and completely why your app
> > needs the data. Starting Spring 2019, all apps submitted to the App Store
> > that access user data are required to include a purpose string. If you're
> > using external libraries or SDKs, they may reference APIs that require a
> > purpose string. While your app might not use these APIs, a purpose
> string is
> > still required. You can contact the developer of the library or SDK and
> > request they release a version of their code that doesn't contain the
> APIs.
> > Learn more (
> >
>