Nine41 Consulting | Is Your Custom Created PLIST Unreadable and in the Incorrect Format?
apple, device management, dep, vpp, systems management, landesk, ivanti, lanrev, absolute, heat, mdm,
653
post-template-default,single,single-post,postid-653,single-format-standard,qode-quick-links-1.0,ajax_fade,page_not_loaded,,columns-3,qode-child-theme-ver-1.0.0,qode-theme-ver-11.0,qode-theme-bridge,wpb-js-composer js-comp-ver-5.1.1,vc_responsive
 

Is Your Custom Created PLIST Unreadable and in the Incorrect Format?

Is Your Custom Created PLIST Unreadable and in the Incorrect Format?

Recently I’ve been building all sorts of custom scripts; writing the outputs to a PLIST file. Some of the custom scripts are simple with only a line or two of outputs being written, but other PLIST files have been much more complex with hundreds of output lines.

Despite my best efforts in paying attention to all of the small details, such as ensuring I have properly typed in the correct syntax for each key, occasionally I’ll run into an error when I try to open the PLIST file with Xcode.

Data Couldn't Be Read

I should mention that TextWrangler will open and display the file just fine.  So using Xcode is a good way to validate your PLIST file has been properly built.

Luckily, OS X includes a utility, plutil, that will give you the exact line number and hopefully an insightful error code as to what the issue is.  To use the utility, all you need to do is follow the 2 steps below.

  1. Launch Terminal
  2. Type in plutil /path/to/your/file/filename.plist

PLUTIL CommandI like to just drag my file into the Terminal window and let the path properly populate.  It’s up to you, you can drag in your file or you can type it out manually. After so doing, you should receive some information similar to the text below.

Knowing my error was on line 12, using TextWrangler I opened the file to see what I was writing to line 12 in my output file.  In this specific example, line 12 shows that I forgot to close out the integer key.

BadOutputPlistA quick fix to add in the “<” bracket to my script and now my PLIST is fully functioning and when the LANDESK scanner processes it, I can be more confident the attributes will properly insert.

No Comments

Post A Comment

ARE YOU READY TO GET STARTED?
Please fill out your information, and a specialist will reach out to discuss our services in more details.
Your Information will never be shared with any third party.
        
Free Training Videos
Register to gain access to all of our free content.
YOUR PHONE
YOUR NAME
YOUR EMAIL
        
Get Started
Provide us your contact information and we will reach out as quickly as possible.
YOUR PHONE
YOUR NAME
YOUR EMAIL
        
Additional Questions?
Provide us your contact information and we will reach out as quickly as possible.
YOUR PHONE
YOUR NAME
YOUR EMAIL
        
Pay by PO?
Provide us your contact information and we will reach out to help you sign up by PO.
YOUR PHONE
YOUR NAME
YOUR EMAIL
Subscribe Now
Subscribing to our site gives you access to our Apple Admin 101 training videos as well as allowing us to notify you of each new blog post we release.
YOUR PHONE
YOUR NAME
YOUR EMAIL
Pay by PO
Send us your contact information and we will reach out to help you sign up by PO.
YOUR PHONE
YOUR NAME
YOUR EMAIL
Additional Questions?
Send us your contact information and your questions and we will reach out as quickly as possible.
YOUR PHONE
YOUR NAME
YOUR EMAIL
YOUR QUESTIONS
Get Started
Provide us your contact information and we will reach out as quickly as possible.
YOUR PHONE
YOUR NAME
YOUR EMAIL
Free Training Videos
Subscribing to our site gives you access to our Apple Admin 101 training videos as well as allowing us to notify you of each new blog post we release.
FIRST NAME
LAST NAME
PHONE
EMAIL
Subscribe Now
Subscribing to our site gives you access to our Apple Admin 101 training videos as well as allowing us to notify you of each new blog post we release.
FIRST NAME
LAST NAME
PHONE
EMAIL