Out of band assets #285

HayesGordon · 2025-01-09T14:29:27Z

This PR adds out of band asset support to Rive React Native.

Please take a look at the video below for an overview of the implementation and an exploration of the provided example.
Feedback is appreciated while this is a work in progress

rev file used in the video:
out_of_band.rev.zip

Video:
https://drive.google.com/file/d/1jDZY2MRLhLfV8EOpRz3rVcCRbTdkv6sI/view?usp=sharing

Edit:

Added android

HayesGordon · 2025-01-10T16:18:14Z

android/src/main/java/com/rivereactnative/RiveReactNativeView.kt

+
+    val source = assetData?.getMap("source") ?: return false // Do not handle the asset.
+
+    CoroutineScope(Dispatchers.IO).launch {


@ErikUggeldahl, your input here would be great on the best way to implement coroutine scope management (canceling it if the view is destroyed).

HayesGordon · 2025-01-10T16:20:33Z

android/src/main/java/com/rivereactnative/RiveReactNativeView.kt

+
+    // Handle release mode (URL instead of asset id)
+    // Resource needs to be loaded in release mode
+    // https://github.com/facebook/react-native/issues/24963#issuecomment-532168307


@lancesnider would be great if we can give extra testing on this. It's handled differently between a dev and release build.

HayesGordon · 2025-01-10T16:22:13Z

src/Rive.tsx

@@ -104,6 +108,10 @@ type Props = {
  testID?: string;
  alignment?: Alignment;
  artboardName?: string;
+  /**
+   * @experimental This is an experimental feature and may change without a major version update (breaking change).


Opinions on marking this as experimental?

I think it's probably a good idea, especially since we're likely to have a major overhaul of the runtime relatively soon.

lancesnider

This is looking great!

I really like the assetsHandled object. I think it'll be easier for users to grasp than assetLoader which requires some extra steps. If I'm understanding correctly the downside is that you can only define a referenced asset at load time, but not at runtime. I'm assuming that has to do with the limitation you mentioned in the video where we can't have a callback?

I love that you don't need to add assets to Bundled Assets in iOS, but I'm not sure I understand why.

lancesnider · 2025-01-10T19:43:57Z

example/src/OutOfBandAssets.tsx

+              //   path: 'fonts', // only needed for Android assets
+              // },
+            },
+            'referenced-image-2929282': {


Though I'd prefer not to need the ID, I think using it by default is probably necessary, given the fact that it's possible to have multiple assets with the same name. I could see users being very confused when both fonts named Tomorrow display the same even though one of them is actually supposed to be a different weight.

I really like the idea of being able to override the default behavior with includeId. Do you have thoughts on that being a global attribute, rather than on a per-asset basis?

For the same fonts (or asset) we will use the same ID! You also have the option to rename these to anything you'd like.

Expanding this APIs ability is something we can also add in the future, if needed.

lancesnider · 2025-01-10T19:48:52Z

example/src/OutOfBandAssets.tsx

+          //
+          // The key of the map is the unique asset identifier (as exported in the Editor),
+          // which is a combination of the asset name and its unique identifier.
+          assetsHandled={{


What's your thinking on the name assetsHandled? My first thought would be to call this referencedAssets to align it with the naming in the editor, but maybe that's too restricting.

I've also been toying with thinking of a different name for this.

I like referencedAssets as a name!

lancesnider · 2025-01-10T19:55:55Z

src/Rive.tsx

@@ -104,6 +108,10 @@ type Props = {
  testID?: string;
  alignment?: Alignment;
  artboardName?: string;
+  /**
+   * @experimental This is an experimental feature and may change without a major version update (breaking change).


I think it's probably a good idea, especially since we're likely to have a major overhaul of the runtime relatively soon.

lancesnider · 2025-01-10T20:15:43Z

src/types.ts

+  sourceAsset?: string;
+  sourceAssetId?: string;
+  path?: string;
+}


Is it worth being explicit that exactly one of sourceUrl, sourceAsset and path is required?

type FileAssetSource = | { sourceUrl: string sourceAsset?: never path?: never sourceAssetId: string } | { sourceAsset: string sourceUrl?: never path?: never sourceAssetId: string } | { path: string sourceUrl?: never sourceAsset?: never sourceAssetId: string } ```

You mean as a doc comment? Or do you have a suggestion code wise?

This as TypeScript should ensure that only one of sourceUrl, sourceAsset, or path is provided at a time

With the current code, it would still be valid if sourceUrl, sourceAsset, path, and sourceAssetId were all undefined. It would also be valid if all 4 were defined.

If you want the type to expect exactly 1 of the 4 values, you might write it like this:

export type FileAssetSource = | { sourceUrl: string; sourceAsset?: never; sourceAssetId?: never; path?: never } | { sourceAsset: string; sourceUrl?: never; sourceAssetId?: never; path?: never } | { sourceAssetId: string; sourceUrl?: never; sourceAsset?: never; path?: never } | { path: string; sourceUrl?: never; sourceAsset?: never; sourceAssetId?: never };

Ahh sorry @lancesnider, I thought you were quoting code above that was already there 🤦 . Yes, this makes sense to add

@lancesnider I played around with this, and this might have other unintended side effects.

The source_ props are not intended to be set directly by the user. I should have actually named the path above sourcePath. They will be mapped from the user supplied value.

So if a user sets any of the source_ options it will fail to work. For simplicity let's keep it as is, and make this a documentation concern.

Yep, this was definitely a nitpick. Let's not worry about it. 👍

lancesnider · 2025-01-10T20:26:10Z

example/src/OutOfBandAssets.tsx

+              //   path: 'images', // only needed for Android assets
+              // },
+            },
+            'referenced_audio-2929340': {


There's no scenario where the asset IDs might change, is there? For example, if the Rive file gets copied or if you reimport a PSD? That could be painful if you have a giant object with ID's included.

That's why the approach for the other runtimes are a callback mechanism where you can read the name + id and query the file. That's not possible for React Native at this stage, which is why this API is different.

The best way to circumvent this is to provide a "name" only fallback and forgo the id

Adds clarity and formatting.

Couple more quick formatting changes.

dan-phantom · 2025-01-13T11:44:59Z

Great work and thank you so much for doing this ❤️

I'm not sure what is the "ID" tbh, how would we obtain it so we know what to set the key to, but if it it depends on the riv animation file I see an issue where some assets (fonts probably more common) is shared between multiple animation files. (we actually have this case #271 (comment))

Thank you

dskuza

There may be some more RN-specific comments left, but generally from the Swift side of things, things look great! I left some comments about things we previously discussed during a live walkthrough.

dskuza · 2025-01-09T15:45:03Z

ios/RNRiveError.swift

@@ -64,6 +64,10 @@ func createMalformedFileError() -> NSError {
    return NSError(domain: RiveErrorDomain, code: RiveErrorCode.malformedFile.rawValue, userInfo: [NSLocalizedDescriptionKey: "Malformed Rive File", "name": "Malformed"])
 }

+func createAssetFileError(_ assetName: String) -> NSError {
+    return NSError(domain: RiveErrorDomain, code: RiveErrorCode.malformedFile.rawValue, userInfo: [NSLocalizedDescriptionKey: "Could not load Rive asset: \(assetName)", "name": "Malformed"])


Nitpicky, but I would maybe use .fileNotFound rather than malformed as the error code.

dskuza · 2025-01-13T15:36:30Z

example/src/OutOfBandAssets.tsx

+          //
+          // The key of the map is the unique asset identifier (as exported in the Editor),
+          // which is a combination of the asset name and its unique identifier.
+          assetsHandled={{


I've also been toying with thinking of a different name for this.

dskuza · 2025-01-13T15:40:33Z

ios/RiveReactNativeView.swift

+        }
+    }
+
+    private func processAssetBytes(_ data: Data, asset: RiveFileAsset, factory: RiveFactory) {


It might be worth having another check here to validate that data.isEmpty == false.

dskuza · 2025-01-13T15:41:24Z

ios/RiveReactNativeView.swift

+    }
+
+    private func splitFileNameAndExtension(fileName: String) -> (name: String?, ext: String?)? {
+        let components = fileName.split(separator: ".")


Do we have any documentation surrounding naming? This might not work as intended, for example, if a user has an asset name with a . in it.

Good catch. See commit: 554fd77

Using Swift provided methods now

dskuza · 2025-01-13T15:43:20Z

ios/RiveReactNativeView.swift

+        return (name: String(components[0]), ext: String(components[1]))
+    }
+
+    private func loadResourceAsset(sourceAsset: String, path: String?, listener: @escaping (Data) -> Void) {


Discussed live, but path is currently ignored. This is understandable as a first-pass, with the expectation being that the file is already in the bundle's Resources directory. There may be a time where we wish to expand this API to support further paths.

tslater · 2025-01-15T16:19:11Z

Love the ability to load assets different ways. As mentioned by others, we still really need the ability to replace an asset at run time. For our use case, we have an image that represents a topic. The user can shuffle this topic, so the current image gets replaced with another image. These images are dynamic (UGC). So we only know them at run time. In our case we'd want have two referenced images that we toggle between, allowing a the theoretically infinite number or images to be displayed as there is no hard limit to the number of shuffles.

If that was too long to follow: we have a need for the API to also allow us to replace an image after the animation loads any number of times, like the JS web rumtime supports (though I do think this API is simpler/cleaner so if there's a way to combine the ideas that would be awesome).

iamrestrepo · 2025-01-30T16:21:00Z

Thanks for doing this! This is definitely something we can take a lot of advantage from and reduces some of the limitations we are currently experiencing.

tslater · 2025-01-30T22:48:40Z

@HayesGordon I'm wondering if I misunderstood something. @lancesnider said "the downside is that you can only define a referenced asset at load time, but not at runtime," so I assumed that was the case. In the video you talked about "hot reloading" so I thought you meant during development, but looking at the code, It looks to me like we can hotswap the assets in production builds. For example, if the references/urls in the assetsHandled map change, they'll be updated in the Rive view without reloading the animation. Am I correct?

Other thoughts after watching the video 4 times:

love the error handling and messages for bad assets (would be awesome to do this for stateMachine/animation names as well instead of crashes)
as far as the id goes, I don't have a strong preference there, but how do you get the ID? I'm not seeing an id in the editor. Is that something you need to get with code somehow?
With my new understanding of updating props to update assets, I think this is a simple API with no limitations I can think of.

lancesnider · 2025-01-31T05:35:06Z

@HayesGordon I'm wondering if I misunderstood something. @lancesnider said "the downside is that you can only define a referenced asset at load time, but not at runtime," so I assumed that was the case. In the video you talked about "hot reloading" so I thought you meant during development, but looking at the code, It looks to me like we can hotswap the assets in production builds. For example, if the references/urls in the assetsHandled map change, they'll be updated in the Rive view without reloading the animation. Am I correct?

Sorry, that was poor phrasing. I meant that this lets you load a different font at runtime, but only when the Rive element first loads for the user. You couldn't keep a reference to the asset and swap it after the Rive has loaded.

garfieldnate · 2025-01-31T06:26:22Z

This looks really promising and I'm excited to use it! This will unblock some Android development efforts for us.

tslater · 2025-01-31T10:19:56Z

Sorry, that was poor phrasing. I meant that this lets you load a different font at runtime, but only when the Rive element first loads for the user. You couldn't keep a reference to the asset and swap it after the Rive has loaded.

@lancesnider What you want can be accomplished with this API (and, if I understand the code correctly, it is already implemented in this PR). The term I would use here is "hot swapping": being able to change the font, image, sound, etc. for an animation without reloading or otherwise interrupting the animation state.

In the web API there is a reference, but in this API you would just update the value of the prop.Props values at initial render:

<Rive
  url="https://domain.com/animation.riv"
  artboardName="Artboard"
  assetsHandled={{
    "Inter-594377": { source: require("./assets/Inter-variant-1.ttf")}
  }}
/>;

Change the value of Inter-594377 to hot swap the image for a new one without disrupting or reinitializing the animation, preserving its state:

<Rive
  url="https://domain.com/animation.riv"
  artboardName="Artboard"
  assetsHandled={{
    "Inter-594377": {source: require("./assets/Inter-variant-2.ttf")}
  }}
/>;

john-sportshub · 2025-02-01T01:55:27Z

This is an awesome feature! I will definitely be using this because my company asked me to do a POC to move all our RN graphics to Rive. The major issue was not being able to remotely load headshots for our items into the template. I'm hoping this gets merged and released soon.

HayesGordon · 2025-02-03T20:07:21Z

Great work and thank you so much for doing this ❤️

I'm not sure what is the "ID" tbh, how would we obtain it so we know what to set the key to, but if it it depends on the riv animation file I see an issue where some assets (fonts probably more common) is shared between multiple animation files. (we actually have this case #271 (comment))

Thank you

The ID comes from the editor when you export the asset! And yes, this will still allow you to reuse assets. But maybe we need to allow you to optionally pass the ID, else it will only use the name of the asset.

lancesnider · 2025-02-03T23:32:08Z

src/types.ts

+  sourceAsset?: string;
+  sourceAssetId?: string;
+  path?: string;
+}


With the current code, it would still be valid if sourceUrl, sourceAsset, path, and sourceAssetId were all undefined. It would also be valid if all 4 were defined.

If you want the type to expect exactly 1 of the 4 values, you might write it like this:

export type FileAssetSource = | { sourceUrl: string; sourceAsset?: never; sourceAssetId?: never; path?: never } | { sourceAsset: string; sourceUrl?: never; sourceAssetId?: never; path?: never } | { sourceAssetId: string; sourceUrl?: never; sourceAsset?: never; path?: never } | { path: string; sourceUrl?: never; sourceAsset?: never; sourceAssetId?: never };

HayesGordon · 2025-02-04T19:18:31Z

See commit: 5138fa4

We will now prefer name+id, and if not found, fallback to only the name.

HayesGordon · 2025-02-05T12:39:05Z

Sorry, that was poor phrasing. I meant that this lets you load a different font at runtime, but only when the Rive element first loads for the user. You couldn't keep a reference to the asset and swap it after the Rive has loaded.

@lancesnider What you want can be accomplished with this API (and, if I understand the code correctly, it is already implemented in this PR). The term I would use here is "hot swapping": being able to change the font, image, sound, etc. for an animation without reloading or otherwise interrupting the animation state.

In the web API there is a reference, but in this API you would just update the value of the prop.Props values at initial render:
<Rive
  url="https://domain.com/animation.riv"
  artboardName="Artboard"
  assetsHandled={{
    "Inter-594377": { source: require("./assets/Inter-variant-1.ttf")}
  }}
/>;
Change the value of Inter-594377 to hot swap the image for a new one without disrupting or reinitializing the animation, preserving its state:
<Rive
  url="https://domain.com/animation.riv"
  artboardName="Artboard"
  assetsHandled={{
    "Inter-594377": {source: require("./assets/Inter-variant-2.ttf")}
  }}
/>;

@tslater we will add this as a separate PR

tslater · 2025-02-05T14:17:22Z

@HayesGordon super pumped about the release!

To confirm, hot swapping assets after initial animation load is possible with this API, but not implemented in this PR/release (8.4.0) but will be in a future PR/release by just the values in the assetsHandled prop?

HayesGordon · 2025-02-05T15:56:41Z

@HayesGordon super pumped about the release!

To confirm, hot swapping assets after initial animation load is possible with this API, but not implemented in this PR/release (8.4.0) but will be in a future PR/release by just the values in the assetsHandled prop?

Basically, yes! I'm thinking on the Rive object after loading you can set an asset by it's name+id (or just name), and then pass in one of the asset loader options. For example:

riveRef.current?.setAsset("Inter-594377", require('./assets/Inter-594377.ttf');

tslater · 2025-02-05T23:38:00Z

@HayesGordon I just tried to load oob assets using [email protected]. I first tried the holo_card.riv example from web, porting it over to RN. Couldn't see the image.

Them I tried copying the out_of_band.riv examples from the RN repo, but it didn't work either. I tried downloading this file from the top of this thread:
out_of_band.rev.zip

I re-exported in the editor and the filename of the referenced image exported was referenced-image-3385083.png so I tried that id. I also tried just the name without the id. I'm not having any luck loading images.

I also tried the font/audio files (but with a lot less effort) and those seem to not be loading either. Not sure if I'm missing a step?

HayesGordon · 2025-02-06T07:55:40Z

@

@tslater are you including the out of band assets:

referencedAssets={{
  'Inter-594377': {
    source: require('./assets/Inter-594377.ttf'),
    // source: {
    //   fileName: 'Feather.ttf',
    //   path: 'fonts', // only needed for Android assets
    // },
  },
  'referenced-image-2929282': {
    source: require('./assets/referenced-image-2929282.png'),
    // source: {
    //   uri: 'https://picsum.photos/id/270/500/500',
    // },
    // source: {
    //   fileName: 'referenced-image-2929282.png',
    //   path: 'images', // only needed for Android assets
    // },
  },
  'referenced_audio-2929340': {
    source: require('./assets/referenced_audio-2929340.wav'),
    // source: {
    //   fileName: 'referenced_audio-2929340.wav',
    //   path: 'audio', // only needed for Android assets
    // },
  },
}}

I just tried with the packaged version 8.4.0 and it's working my side.

Are you seeing any errors if you subscribe to onError:

onError={(riveError: RNRiveError) => {
  console.log(riveError);
}}

If you're still encountering issues, can you make a sample project and share that so we can investigate.

tslater · 2025-02-06T08:58:08Z

I tried both requiring them (and including them) and remote uris. I am subscribed to errors but no errors. I'll try a fresh project and let you know.

tslater · 2025-02-06T13:15:50Z

For reference, I am using an expo dev client on iOS. Here's a sample project:

https://github.com/tslater/rive-test-oob-assets

@HayesGordon

HayesGordon · 2025-02-06T13:41:18Z

For reference, I am using an expo dev client on iOS. Here's a sample project:

https://github.com/tslater/rive-test-oob-assets

@HayesGordon

Tagging @lancesnider as he mentioned testing things on Expo, maybe he has some insight as well.

john-sportshub · 2025-02-06T21:45:55Z

I tried both requiring them (and including them) and remote uris. I am subscribed to errors but no errors. I'll try a fresh project and let you know.

I am running into this as well, there is no error, but the image is not loading.

I am using expo with dev builds.

@HayesGordon I can create a reproducible example if needed. Let me know and thanks for the work on this!

lancesnider · 2025-02-06T21:47:17Z

@tslater Good news! I just got your example file working. Here are the 3 things I did:

First I had to prebuild the Expo app to get the native libraries working. I'm assuming you did this as well if you were able to get the .riv working without the referenced assets. If not, here are the steps:

npx expo prebuild
cd ios
pod install

Next I needed to make sure the assets and the .riv were being copied into the bundle.

In XCode select rivetestobassets in the sidebar and go to the Build Phases tab
Add the .riv and the referenced assets to the Copy Bundle Resources

At this point, the .riv was displaying, but the referenced assets weren't. It looks like it was trying to load the wrong .riv. When setting the resourceName directly, it worked:

// before
resourceName={!uriIsUrl ? resolved.uri : undefined}
url={uriIsUrl ? resolved.uri : undefined}

// after
resourceName='out_of_band'

With these changes I was able to run yarn ios and see it working:

tslater · 2025-02-06T21:53:33Z

@lancesnider Thanks for checking this out so quickly!
Were you able to get the url sources working?
The benefits we're looking to get from OOB assets is from loading them remotely, so bundling assets isn't an option in our requirements.

For examoke, does this work?

    'referenced-image-3385083': {
      source: {
        uri: 'https://upload.wikimedia.org/wikipedia/commons/4/47/PNG_transparency_demonstration_1.png',
      },
  },

john-sportshub · 2025-02-07T00:55:20Z

@lancesnider Thanks for checking this out so quickly! Were you able to get the url sources working? The benefits we're looking to get from OOB assets is from loading them remotely, so bundling assets isn't an option in our requirements.

For examoke, does this work?
    'referenced-image-3385083': {
      source: {
        uri: 'https://upload.wikimedia.org/wikipedia/commons/4/47/PNG_transparency_demonstration_1.png',
      },
  },

@tslater I was able to get the remote URI loading working following his steps.

What I am still struggling with is if the Rive file is not a local asset in the bundle. If I load the Rive file from a url such as https://images.gameblazers.com/example.riv the referenced assets wont work. Not sure if this intended or not though.

tslater · 2025-02-07T02:26:25Z

@john-sportshub That is a good catch. So it seems lik OOB assets currently does not work for rive animations that are loaded via URL.

HayesGordon · 2025-02-07T06:48:17Z

@tslater and @john-sportshub, I'll push a fix for getting OOB assets to work when using a URL.

Edit: this requires a change in the underlying iOS runtime first

tslater · 2025-02-07T18:20:10Z

@HayesGordon Bummer about the needed changes to the iOS runtime, but bug thanks for being so on top of this.
I'm assuming that will delay the change a bit? We'll see if we can change our workflow temporarily to test this with bundled rive animations in the meantime.

HayesGordon · 2025-02-10T17:31:39Z

@tslater it should be a small change, but it depends on when we will be able to do a new iOS release. There are other conflicting work that might block a release. I'm hoping we can get it out this week

tslater · 2025-02-19T20:26:48Z

@HayesGordon Is there a separate issue for it, or are we tracking here?

HayesGordon added 5 commits January 9, 2025 15:55

docs: improve instructions

5f78cfc

feat: add out of band assets

b93e18c

feat: add out of band assets ios

38809f8

chore: add out of band asset example

ae0dcc2

chore: cleanup oob example

5499e4f

HayesGordon requested review from dskuza, ErikUggeldahl and lancesnider January 9, 2025 14:29

HayesGordon mentioned this pull request Jan 9, 2025

OOB Asset Support #278

Closed

HayesGordon added 3 commits January 10, 2025 10:16

docs: formatting

a622e39

feat: out of band assets android

385d8da

chore: android example out of band assets

d90b1ad

HayesGordon commented Jan 10, 2025

View reviewed changes

chore: fix comment

de4e684

HayesGordon commented Jan 10, 2025

View reviewed changes

This was referenced Jan 10, 2025

Asset Handler API Compatibility with React Native #236

Closed

assetLoader for RN ? #271

Closed

chore: remove logs and empty lines

cc84f03

lancesnider reviewed Jan 10, 2025

View reviewed changes

ErikUggeldahl added 2 commits January 10, 2025 18:49

Update CONTRIBUTING.md

5772ea2

Adds clarity and formatting.

Further updating CONTRIBUTING.md

68bd17e

Couple more quick formatting changes.

dskuza approved these changes Jan 13, 2025

View reviewed changes

lancesnider approved these changes Feb 3, 2025

View reviewed changes

HayesGordon added 6 commits February 4, 2025 16:39

refactor: restric FileAssetSource types

3538673

refactor: revert FIleAssetSource types

0af9ec1

refactor: rename assetsHandled

56d2832

chore: ios account for period in filename

554fd77

chore: apply ios feedback

78c15c8

feat: fallback to only use the asset name as a key

5138fa4

feat: android cancel coroutine scope and job on dispose

686d152

HayesGordon merged commit 813075b into main Feb 5, 2025
1 check passed

HayesGordon deleted the out-of-band-assets branch February 5, 2025 12:39


		val source = assetData?.getMap("source") ?: return false // Do not handle the asset.

		CoroutineScope(Dispatchers.IO).launch {

Out of band assets #285

Out of band assets #285

Conversation

HayesGordon commented Jan 9, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lancesnider left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dan-phantom commented Jan 13, 2025

dskuza left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tslater commented Jan 15, 2025

iamrestrepo commented Jan 30, 2025

tslater commented Jan 30, 2025

lancesnider commented Jan 31, 2025

garfieldnate commented Jan 31, 2025

tslater commented Jan 31, 2025

john-sportshub commented Feb 1, 2025

HayesGordon commented Feb 3, 2025

Choose a reason for hiding this comment

HayesGordon commented Feb 4, 2025

HayesGordon commented Feb 5, 2025

tslater commented Feb 5, 2025

HayesGordon commented Feb 5, 2025

tslater commented Feb 5, 2025

HayesGordon commented Feb 6, 2025

tslater commented Feb 6, 2025

tslater commented Feb 6, 2025 • edited Loading

HayesGordon commented Feb 6, 2025

john-sportshub commented Feb 6, 2025

lancesnider commented Feb 6, 2025

tslater commented Feb 6, 2025 • edited Loading

john-sportshub commented Feb 7, 2025

tslater commented Feb 7, 2025 • edited Loading

HayesGordon commented Feb 7, 2025 • edited Loading

tslater commented Feb 7, 2025

HayesGordon commented Feb 10, 2025

tslater commented Feb 19, 2025

HayesGordon commented Jan 9, 2025 •

edited

Loading

tslater commented Feb 6, 2025 •

edited

Loading

tslater commented Feb 6, 2025 •

edited

Loading

tslater commented Feb 7, 2025 •

edited

Loading

HayesGordon commented Feb 7, 2025 •

edited

Loading