Skip to main content

Posts

Showing posts from June, 2025

Build Failed with an Exception in Android Studio – Gradle Metadata Error

If you're encountering the following error during build in Android Studio: FAILURE: Build failed with an exception. * What went wrong: Multiple build operations failed. Could not read workspace metadata from C:\Users\abc\.gradle\caches\transforms- 4 \488376c3749de4c34a681b5fd5a06aa8\metadata. bin Could not read workspace metadata from C:\Users\abc\.gradle\caches\transforms- 4 \e2dc2f44e335b5e104801cc73d245ee1\metadata. bin This usually indicates corrupted Gradle cache files. How to Fix: Step 1: Open the Terminal in Android Studio (or use Command Prompt). Step 2: Navigate to the Gradle directory: cd C:\Users\<YourUsername>\.gradle\ Step 3: Remove the corrupted caches folder: bash rm -r caches\ On Windows, if using Command Prompt instead of terminal, use: c  rmdir /s /q caches Step 4: Go back to Android Studio and click Build > Clean Project or Rebuild Project . This should resolve the issue and allow your project to build successfully.

Custom Popup Applet in Siebel Returns Error: "Method ShowPopup is not allowed here (SBL-UIF-00348)"

Background: A custom button was created with the method name 'abc' , which triggers a workflow through a Business Component user property. This workflow is designed to open a popup applet that displays a BI Publisher (BIP) report. However, when clicking the button, although the popup applet opens, it displays the following error message inside: Method ShowPopup is not allowed here (SBL-UIF-00348)   Error Message: We detected an error which may have occurred for one or more of the following reasons: Method ShowPopup is not allowed here (SBL-UIF-00348) Debug and Resolution: After reviewing the Siebel Personalization Log, it was observed that following the execution of the custom method 'abc' , Siebel internally calls the 'ShowPopup' method. It turned out that 'ShowPopup' was also being used for another popup applet where it had been explicitly disabled via an Applet User Property ( CanInvoke = FALSE ). For testing purposes, we deactivated ...