After updating to 4.2.2 dev, plugin won't load in logic, trouble parsing plists persist

Looks like the Plugin is invisible to logic, no entry in the plugin manager. Auval shows this error

2016-05-27 09:34:18.365 auvaltool[27341:573301] 09:34:18.364 WARNING:  >compload> 472: MyPlugin.component -- file:///Users/christian/Library/Audio/Plug-Ins/Components/: trouble parsing Info.plist's AudioComponents, key (null); entry: <CFBasicHash 0x7faf53c09e60 [0x7fff7943f440]>{type = mutable dict, count = 7,
entries =>
	2 : <CFString 0x7fff793c9b60 [0x7fff7943f440]>{contents = "manufacturer"} = <CFString 0x7faf53c0ab40 [0x7fff7943f440]>{contents = "MANU"}
	7 : <CFString 0x7fff793cd620 [0x7fff7943f440]>{contents = "factoryFunction"} = <CFString 0x7faf53c0a510 [0x7fff7943f440]>{contents = "MyPluginAUFactory"}
	8 : <CFString 0x7faf53c0ac70 [0x7fff7943f440]>{contents = "subtype"} = <CFString 0x7faf53c0acb0 [0x7fff7943f440]>{contents = "MaPl"}
	9 : <CFString 0x7fff793f17c0 [0x7fff7943f440]>{contents = "description"} = <CFString 0x7faf53c09260 [0x7fff7943f440]>{contents = "MyPlugin"}
	10 : <CFString 0x7fff793f04a0 [0x7fff7943f440]>{contents = "type"} = <CFString 0x7faf53c0ad90 [0x7fff7943f440]>{contents = "kAudioUnitType_Effect"}
	11 : <CFString 0x7fff7937bd20 [0x7fff7943f440]>{contents = "name"} = <CFString 0x7faf53c0ab10 [0x7fff7943f440]>{contents = "Manufacturer: MyPlugin"}
	12 : <CFString 0x7fff793fa440 [0x7fff7943f440]>{contents = "version"} = <CFNumber 0x1000037 [0x7fff7943f440]>{value = +65536, type = kCFNumberSInt64Type}

Update, my Plugin magically appeared again in Logic

To get rid of the trouble parsing plist-problem, i removed
the Plugin AU Main Type - Setting in Projucer, which was

Which kind of values did this form expect?

After rescanning the plugin now, auval creates an

FATAL ERROR: Initialize: result: -10868 <


It expects the four char codes for AudioUnit types, i.e. aufx, aumf, aupn, aumu, aufc, auou, augn, auol etc. If you leave it empty then the projucer will choose the correct four char code depending on if “Is a synth”, “Plugin wants midi input” etc is checked.

Also remember to always re-scan your plug-ins in Logic’s plug-in manager.

Thanks, yes it even was not visible in the plugin-manage (files was there and accessible) However, problem is gone now!
Could resolve the other issue “FATAL ERROR: Initialize: result: -10868” by unchecking “is Synth” checkbox