Adding Android SDK fails on app build

New
Avatar
Enoch Youn

I have an Android app built using Ionic/Capacitor/ReactJS. When I add the FullStory Android SDK and enable the plugin in my file like this:
 

apply plugin: 'fullstory'


fullstory {

org "[REDACTED]

enabledVariants "debug"

logLevel "debug"

logcatLevel "debug"

}

 

I am faced with an error on build:
 

> Task :app:fullstoryDebug
Applying FullStory to variant 'debug'...
FullStory: Detected framework OkHttp
FullStory: Detected framework Http(s)URLConnection
FullStory: Detected framework AndroidX Fragments
FullStory: Detected framework Capacitor

> Task :app:fullstoryDebug FAILED
Execution failed for task ':app:fullstoryDebug'.
> Chunk [ margin–left: 10px] is not a valid entry

 

I have a third-party SDK in the app that I feel like might be causing the problem, I’m just not sure how to debug and find what is causing the CSS-looking “chunk” to be read by Fullstory and what makes it “invalid”

0

Comments

3 comments

  • Avatar
    mohammed.sharfuddeen435

    Hi @eyoung_ss ,
    I hope you're doing well. I see that you're facing an issue with the FullStory Android SDK during the build process, we faced similar issue last month and our tech guy send me this steps which he followed to resolve the same. I’m not much of a techie, see if any of this helps you.

    The error you're encountering indicates that there's a problem with a CSS chunk that FullStory is attempting to process. This may be related to the configuration or interaction with other plugins and frameworks in your Ionic/Capacitor/ReactJS app.
     

    To narrow down the issue and find out which part of your app is causing this, you can consider the following steps:

    1. Check CSS Files: Examine your CSS files, especially those related to styling or layouts. Look for any unusual entries, such as the mentioned [ margin–left: 10px], and correct or remove them.

    2. Third-Party SDK: As you suspect, the error might be related to a third-party SDK in your app. Temporarily disable or remove the third-party SDK and try building again to see if the issue persists. This can help you identify if there's a conflict between FullStory and the third-party SDK.

    3. Build Gradle Configuration: Ensure that your build.gradle configuration for FullStory is correct. It seems like a CSS-related issue, but confirming the configuration is always a good step.

    4. Contact FullStory Support: If the issue persists after trying the above steps, consider reaching out to FullStory support. They might have insights into similar cases or offer guidance specific to FullStory integration with Ionic/Capacitor/ReactJS.

      Remember to test your changes incrementally to pinpoint the exact cause of the issue. I hope this helps, and please feel free to provide more details if you need further assistance.

      Best regards,
      @Sharf 

    0
  • Avatar
    Enoch Youn

    I unzipped the library in question and found a matching string in the values.xml because the vendor has large HTML formatted content blocks in their strings. Had vendor remove the offending CSS string, then it moved down the chain to the next offending string in the same file. Ugh.

    Working with Fullstory tech support at this point to see if we can somehow skip processing their values.xml files during their Gradle app instrumentation step.

    0
  • Avatar
    mohammed.sharfuddeen435

    That’s the good progress, hope things get resolved real quick regarding the set-up and you will enjoy using fullstory soon.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post