Any way to bypass this AppStore prompt?

[Rwjohnson06]

I get this prompt when I attempt to launch a dated application (iDentify) that still worked on Mac OS El Capitan. iDentify will no longer launch after I updated to Mac OS Sierra. Is there a way to bypass this prompt and force launch the application? The developer discontinued support back in 2012 from the looks of it but the app has worked great on all OS version since then and there are ZERO alternatives that work as well.

Thank in advance for everyones time.

 

[fisherking]

try this: http://identify2.arrmihardies.com

 

[Rwjohnson06]

Nope. Delete, log out, reboot, re-download/install does not work. As soon as I attempt to launch it it says its out of date and directs me to the app store to download the same version...

 

[fisherking]

you could probably go into the app's package contents, and edit the info.plist there to accomodate the new OS (maybe). but you'l have to research that, am not an expert.

or... someone else here might have an idea. good luck!

 

[Rwjohnson06]

I've attempted that as well. I've modified certain lines that reference version checking but no dice.

Any ideas as to which lines to modify?

Here's the .plist contents.





<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>10K549</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleDisplayName</key>
<string>iDentify</string>
<key>CFBundleDocumentTypes</key>
<array>
<dict>
<key>CFBundleTypeExtensions</key>
<array>
<string>mp4</string>
<string>m4v</string>
</array>
<key>CFBundleTypeName</key>
<string>Mpeg Files</string>
<key>CFBundleTypeRole</key>
<string>Editor</string>
<key>LSHandlerRank</key>
<string>Default</string>
</dict>
<dict>
<key>CFBundleTypeExtensions</key>
<array>
<string>id2key</string>
</array>
<key>CFBundleTypeName</key>
<string>iDentify 2 Registration Key</string>
<key>CFBundleTypeRole</key>
<string>Editor</string>
<key>LSTypeIsPackage</key>
<false/>
<key>NSPersistentStoreTypeKey</key>
<string>XML</string>
</dict>
</array>
<key>CFBundleExecutable</key>
<string>iDentify</string>
<key>CFBundleIconFile</key>
<string>APPL.icns</string>
<key>CFBundleIdentifier</key>
<string>com.arrmihardies.iDentify2</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>iDentify</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>551</string>
<key>CFBundleVersion</key>
<string>551</string>
<key>DTCompiler</key>
<string></string>
<key>DTPlatformBuild</key>
<string>10M2518</string>
<key>DTPlatformVersion</key>
<string>PG</string>
<key>DTSDKBuild</key>
<string>9L31a</string>
<key>DTSDKName</key>
<string>macosx10.5</string>
<key>DTXcode</key>
<string>0400</string>
<key>DTXcodeBuild</key>
<string>10M2518</string>
<key>LSMinimumSystemVersion</key>
<string>10.5</string>
<key>NSHumanReadableCopyright</key>
<string>2010 Justin Pulsipher</string>
<key>NSMainNibFile</key>
<string>MainMenu</string>
<key>NSPrincipalClass</key>
<string>NSApplication</string>
<key>SUFeedURL</key>
<string>http://dl.dropbox.com/u/1495067/iDentifySparkle/iDentifyAppcast.xml</string>
<key>SUPublicDSAKeyFile</key>
<string>dsa_pub.pem</string>
</dict>
</plist>
[doublepost=1479348928][/doublepost]I found the issue. Objective-C garbage collection is no longer supported in Mac OS Sierra. Now... anyway way around this? Also seriously thanks. I appreciate any help. I love this app and would hate to lose it. Looks like I might lost it if I can't figure this out.

 

[DeltaMac]

Compatibility with Sierra may be as simple as modifying the version checks - or could be that some of the libraries or other parts of the code have been replaced, or deprecated, or different paths, or other changes that prevent the app from working in Sierra. Could be a simple modification, or some major part needs rewriting. I have no experience in fixing older apps, but know that certain elements that existed 6 or 7 years ago are either changed in some minor way, as system software gets updated, or enough different that apps may need complete rewrites.

Do you require Sierra for any other software?
If not, and the IDentify app is important to you, backgrade to El Capitan
What happens when you need to move past El Capitan?

 

[Rwjohnson06]

Compatibility with Sierra may be as simple as modifying the version checks - or could be that some of the libraries or other parts of the code have been replaced, or deprecated, or different paths, or other changes that prevent the app from working in Sierra. Could be a simple modification, or some major part needs rewriting. I have no experience in fixing older apps, but know that certain elements that existed 6 or 7 years ago are either changed in some minor way, as system software gets updated, or enough different that apps may need complete rewrites.

Do you require Sierra for any other software?
If not, and the IDentify app is important to you, backgrade to El Capitan
What happens when you need to move past El Capitan?

The issue is that Objective-C garbage collection is no longer supported in Mac OS Sierra. Is there a way to enable this on Sierra? Is a re-write of the app necessary? Can it be easily ported to work with Sierra using Xcode? Also I would like to continue using Sierra and refrain from down-grading.

 

[KALLT]

The application is ancient and I suspect that Apple simply removed garbage collection from the Obj-C runtime. You’re likely out of luck. This is not something you can fix quickly and I don’t see the source code anywhere.

 

[Ritsuka]

Yes, the developer needed to switch from garbage collection to ARC, a really easy thing to do for a small app like his one. But he rage-quitted for some reason lol.

You can try Subler (shameless plug), the workflow is a bit different btw, but you should be able to do the same things more or less.

 

[KALLT]

The developer refused to switch to Xcode 4 at the time and has decided to stick with Xcode 3 all these years. They probably still used Tiger to compile the last version. Who knows what cruft is in that code by now. Compiling it against a modern SDK is probably not worth the trouble, even if the source code were available. Not to mention that the third-party APIs that the program is using are changing or have changed.