amzn / amzn/fire-app-builder

Configure Feed with Vimeo

Open
#56 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
201
Forks
255
PR merge metrics
No merged PRs in 30d

Description

Hello! I am trying to configure my feed using a Vimeo xml feed and am wondering if there is any known recipe to get it to load properly from Vimeo. Mine just keeps crashing when I build it and I KNOW it has to do with my recipe.

Here's an example of my xml feed:
```

Harry Potter World
Tue, 03 Mar 2020 21:13:59 -0500
https://vimeo.com/395345323
https://vimeo.com/395345323
All

Harry Potter World

Roger Rabbit

```

And my recipe:
{
"cooker": "DynamicParser",
"format": "xml",
"model": "com.amazon.android.model.content.Content",
"translator": "ContentTranslator",
"modelType": "array",
"query": "//item[./title='$$par0$$']",
"queryResultType": "[]$",
"matchList": [
"title/#text@mTitle",
"guid/#text@mId",
"description/#text@mDescription",
"link/#text@mUrl",
"media:content/media:thumbnail/#attributes/url@mCardImageUrl",
"media:content/media:thumbnail/#attributes/url@mBackgroundImageUrl"
]
}

I believe the problem is that the "link" in my xml feed (`https://vimeo.com/395345323`) doesn't link directly to the video, but rather to the Vimeo page the that video is on. The actual video has a very similar web address -----------> `https://player.vimeo.com/video/395345323`

Both have the same ending (`395345323`). I'm pretty new to coding - is there a way I can tell the code to begin with "`https://player.vimeo.com/video/`" and then call the LAST part from the xml file "`395345323`" ?

Thanks for your help!

Contributor guide

Open the contributing guide

Research direction

The issue identifies the DynamicParser XML recipe and its matchList; start by reproducing the build with that recipe and capturing the crash output. Done means the Vimeo feed parses successfully and the app builds without crashing.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, xml
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.