P PJLPJLPJL Member Licensed User Longtime User Oct 15, 2026 #1 I am trying to add the following to my manifest: [CODE lang="xml" title="Manifest Code"]AddProguardText(-assumenosideeffects class android.util.Log { public static *** v(...); public static *** d(...); public static *** i(...); public static *** w(...); public static *** e(...); })[/CODE] and the UI immediately flags this as an error: Error in manifest editor: Error parsing manifest script:<br />Line = 34, Word = ;<br />Command expected. What am I doing wrong please? Thank you.
I am trying to add the following to my manifest: [CODE lang="xml" title="Manifest Code"]AddProguardText(-assumenosideeffects class android.util.Log { public static *** v(...); public static *** d(...); public static *** i(...); public static *** w(...); public static *** e(...); })[/CODE] and the UI immediately flags this as an error: Error in manifest editor: Error parsing manifest script:<br />Line = 34, Word = ;<br />Command expected. What am I doing wrong please? Thank you.
Erel B4X founder Staff member Licensed User Longtime User Oct 16, 2026 #2 Why are these rules needed? Where do they come from? Better to remove them. Closing parenthesis should be escaped like this: Code: AddProguardText(-assumenosideeffects class android.util.Log { public static *** v(...)); public static *** d(...)); public static *** i(...)); public static *** w(...)); public static *** e(...)); }) Upvote 0
Why are these rules needed? Where do they come from? Better to remove them. Closing parenthesis should be escaped like this: Code: AddProguardText(-assumenosideeffects class android.util.Log { public static *** v(...)); public static *** d(...)); public static *** i(...)); public static *** w(...)); public static *** e(...)); })
P PJLPJLPJL Member Licensed User Longtime User Oct 16, 2026 #3 Thank you for this - it has solved the problem. As to why: as a hobbyist I have just one phone which is both my "production" machine running lots of B4A apps including several widgets and persistent services, and my "development" machine where I debug new apps and modifications; and I find that even though I've removed all the log() statements in my working apps, the logs from B4A swamp the log window when I am debugging. This prevents those logs from coming through Upvote 0
Thank you for this - it has solved the problem. As to why: as a hobbyist I have just one phone which is both my "production" machine running lots of B4A apps including several widgets and persistent services, and my "development" machine where I debug new apps and modifications; and I find that even though I've removed all the log() statements in my working apps, the logs from B4A swamp the log window when I am debugging. This prevents those logs from coming through