Futcal is not working about futcal-for-scriptable

[thejosejorge]

FotMob have been changing their API almost every week. This is creating several issues and forcing very frequent fixes.
I am aware of the issue reported, however, before changing anything else, I will wait a couple of weeks and check if the API stabilises.

Thanks,
José

[hangoon-p]

Certainly we will have to wait @thejosejorge 's update for this problem.
In the meantime, you follow my ugly but working solution as below.

You can simply change every ${baseApiUrl}/teams to ${baseApiUrl}/api/teams in the script.

It is easy to do with find and replace function of any text editor.

[hangoon-p]

@beratgashi I am happy for

@hangoon-p i've just added the /api to the defined variable $baseApiUrl and it worked!

Thank you so much dude, you saved my day.

glad it helped you.
have a nice day

[thejosejorge]

@hangoon-p I hadn't had the chance to look for the new API URL format, so thank you for doing that!

Simplest solution was to add the "/api" string only to teamDataApiUrl, since it seems matchDetailsApiUrl or the TapUrls haven't changed (yet). However the behaviour when tapping the different sections seems still a bit unstable.
I have now added this change to the code, but will keep monitoring this - has said FotMob have been changing their API almost every week.

Thanks,
José

[beratgashi]

+1

[j43h4k]

OK. I really need this. Thank you for information and your work.

[beratgashi]

@thejosejorge i miss this widget man 😣

[beratgashi]

@hangoon-p i've just added the /api to the defined variable $baseApiUrl and it worked!

Thank you so much dude, you saved my day.

[beratgashi]

@thejosejorge can you please tell me how can i make rounded the highlightedRow

[thejosejorge]

Hi @beratgashi,
The "showRowPositionHighlight" is using the table cells color to add the highlight so it can't be rounded. If you want to have a rounded effect you would need to use the same approach I use for "showCirclePositionHighlight", adding the highlight as an image - although this is not a trivial change.

Closing the ticket as the original issue is fixed.