Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Atsushi Eno
    @atsushieno
    @MakarkinPRO remove references to Fabric.Sdk.Platform and anthing that indirectly references it.
    Maybe you are either mixing different versions (where assembly set differs) or referencing that is not supposed to be "installed and/or run on Android target" e.g. "development environment only" assemblies.
    @HariharanArumugam isn't sqllite database just a file? Then you can use "adb push" and "adb pull"
    You specify the file name when opening sqlite database by yourself, right?
    (haven't used it by myself, I may be wrong)
    MakarkinPRO
    @MakarkinPRO
    @atsushieno sorry didnt' get where to delete Fabric.Sdk.Platform?
    Atsushi Eno
    @atsushieno
    So you didn't add Reference to Fabric.Sdk.Platform.dll directly by yourself.
    MakarkinPRO
    @MakarkinPRO
    complitl confuse what to do)
    Atsushi Eno
    @atsushieno
    When building Xamarin.Android application project, we track assembly references etc. and add them as references, recursively (your Reference assembly usually references further asseblies).
    My assumption of the situation is, one of your assemblies references FooBar.dll, and FooBar.dll references Fabric.Sdk.Platform.dll. So you'll have to find and remove such a reference assembly from your References.
    MakarkinPRO
    @MakarkinPRO
    So I need edit the DLL file?
    blob
    thats what I need to edit?
    Atsushi Eno
    @atsushieno
    Oh you have references to both Fabric.dll and FabricSdk.dll in your project. Then that's sipmple: remove one of those
    from the solution pad (right pane)
    (Can't type Cyrillic script so I cannot point exactly, sorry lol)
    MakarkinPRO
    @MakarkinPRO
    just delete Fabric
    it's came up with 100+ errors)
    Atsushi Eno
    @atsushieno
    sounds like a progress
    ... or not; it just lost required assembly :p
    what if you do otherwise; bring back Fabric.dll and delete FabricSdk and FabricSdk.Platform ?
    MakarkinPRO
    @MakarkinPRO
    try that
    nope it's have another error when I delete files
    Atsushi Eno
    @atsushieno
    Where is your Fabric.dll from?
    I assume your FabricSdk.* are from https://github.com/drungrin/Fabric.Sdk.Xamarin/tree/master/Sources
    MakarkinPRO
    @MakarkinPRO
    yes!
    Atsushi Eno
    @atsushieno
    But there is no Fabric.dll, so I guess you got it from other package
    MakarkinPRO
    @MakarkinPRO
    let me check
    Atsushi Eno
    @atsushieno
    Maybe it's from a package that shipped TwitterCore.Platform?
    MakarkinPRO
    @MakarkinPRO
    https://github.com/muhaym/Fabric.Sdk.Xamarin
    Atsushi Eno
    @atsushieno
    That's a fork of the project I mentioned above, and it does not seem to contain "Fabric.dll"
    MakarkinPRO
    @MakarkinPRO
    know I really confuse of how to I got that file)
    Atsushi Eno
    @atsushieno
    Where is your TwitterCore.Platform from?
    nuget package? Package name?
    MakarkinPRO
    @MakarkinPRO
    when I openning a Project in Xamarin I see that ICONs
    blob
    after that I push manuall ADD LINK, and choosen that files from the Folder... (but know cannot find them)
    hah it's appering. When I pushing on the NUget packages
    after that it's creating
    blob
    after that I adding ADD LINKs manually and trying tio build a project
    may be I'm doing something wrong?
    Atsushi Eno
    @atsushieno
    It seems DigitsKit is also from Twitter
    MakarkinPRO
    @MakarkinPRO
    looks like ORIGINAL github don't have Fabric
    blob
    Atsushi Eno
    @atsushieno
    So, DigitsKit~.dll references TwitterCore~.dll, and it recursively references Fabric.dll
    MakarkinPRO
    @MakarkinPRO
    but when I complinig it's have a a bunch more errors )
    any ideas what to do? )
    Atsushi Eno
    @atsushieno
    Going back to the resulting errors, you cannot have both Fabric.dll and Fabric.Sdk~.dll. Because they both reference one Java type and we need to have one-by-one map (so that JNI invocation to forward to managed type can be consistent).
    MakarkinPRO
    @MakarkinPRO
    ok