Apple is making it worse.
    
    As March 10, the Transporter/App Store (it seems) will 
    
    a) verify to app (I am on a new Mac with a fresh set of certs and 
provisioning profiles)
    b) then, accept delivery of the app 
    c) then respond with :"DELIVERRY FAILED ON MAR 10, 2020, AT 11:48 AM".   1 
Issue
    d). ERROR ITMS-90339: "This bundle is invalid. The Info.plist contains an 
invalid key 'UIApplicationExitsOnSuspend' in bundle SivaSiva [SivaSiva.app]"
    
    Usually after an hour or so, the build would appear, despite the error and 
you could go to TestFlight. Now after 3 hours, the build will not appear.
    
    AND
     
    If you can edit the pList on in standalone, we get another error on attempt 
thru Transporter:
    
    ERROR ITMS-90035: "Invalid Signature. Invalid Info.plist (plist or 
signature have been modified). The file at path [SivaSiva.app/SivaSiva] is not 
properly signed. Make sure you have signed your application with a distribution 
certificate, not an ad hoc certificate or a development certificate. Verify 
that the code signing settings in Xcode are correct at the target level (which 
override any values at the project level). Additionally, make sure the bundle 
you are uploading was built using a Release target in Xcode, not a Simulator 
target. If you are certain your code signing settings are correct, choose 
"Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild 
your release target. For more information, please consult 
https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html";
    
    I guess I have to edit the .plist in the 9.6.dp2 build resources...
    
    Another day lost to Apple....
    
    
    On 6/12/19, 11:31 AM, "Sannyasin Brahmanathaswami" <bra...@hindu.org> wrote:
    
        Yes, I tried to re-upload after deleted in the key (without checking 
iTunes first) and it turns out the first app was accepted..., "redundant 
build'' on the 2nd attempt. I went into iTunesConnect and and the app is now in 
for review by the Lords of Apple.
        
        Agreed. We need to find out what "gives" with this key being deleted.
        
        Maybe we well get a "resume" message from  iOS to the LC in the 
engine... that would be interesting.
        
        BR
        
        
        On 6/12/19, 8:20 AM, "Ralph DiMola" <rdim...@evergreeninfo.net> wrote:
        
            Apparently ALL apps will NOT "exit on suspend" in iOS 12+. The real
            question is if we eliminate this key too soon then what will 
happened to pre
            iOS 12 installs? I think for now we should keep this key and live 
with the
            warnings.
        On 6/12/19, 8:20 AM, "Ralph DiMola" <rdim...@evergreeninfo.net> wrote:
        
            I had this problem last week. I have a ticket out but am unable to 
work on
            it because our office is moving and we are in shambles. This is 
just a
            warning and your .app will be processed and approved for submission 
for app
            review. Apparently ALL apps will NOT "exit on suspend" in iOS 12+. 
The real
            question is if we eliminate this key too soon then what will 
happened to pre
            iOS 12 installs? I think for now we should keep this key and live 
with the
            warnings.
        
        
    
    

_______________________________________________
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

Reply via email to