Is anyone else (who has roku billing active) having issues loading the “transaction details” page? I have tried different browsers, clearing the cache, etc. Its been like this for a few days now.
Thanks!
Is anyone else (who has roku billing active) having issues loading the “transaction details” page? I have tried different browsers, clearing the cache, etc. Its been like this for a few days now.
Thanks!
I’m able to get to it.
It’s periodically very slow for me, but loads eventually. In fact, the developer portal, in general, is painfully slow overall.
Do not use the “new site” report https://developer.roku.com/transactions
Instead use the “old site” report https://owner.roku.com/Developer/Transactions
The “reimagined” site Reports section is an unmitigated disaster that starts bombing when reaching significant number of transactions. I am guessing the reason is the awful HTML generated for the tables, for example a single transaction from the old site is 248 chars:
"https wrote:
12/01/15
17684638
Sale
1A7F3110-6F96-4E99-A402-A56001169350
Agario - beta$0.00
CAD
The very same transaction blows up to 3005 characters due to ver-bogosity:
"https wrote:
Channel Name
Agario - beta
Transaction ID
1A7F3110-6F96-4E99-A402-A56001169350
Roku Account
17684638
Transaction Type
Sale
Amount
$ 0.00
CAD
Product ID
Expiration Date
Partner Reference ID
Original Transaction ID
Original Purchase Date
Reason
Comments
Why do we care? Well this was a single line/item from the table - one download or purchase. The “payoff” comes when there are thousands of transactions and the browser will need 3005/248 = ~12 times the memory. Particularly offensive are the unused data-reactid attributes, there are 40 of them per txn, each setting a distinct name string. The problems start when a developer has big number of app installs, then browser tab RAM usage explodes and the tab will likely crash.
Can the web developer that produced this ReactJS-ive sludge - kindly descend here to explain the need for it? I am sure with shared efforts we can trim down the lard off this memory hog, it’s in our common interest!
PS. To compare RAM used, i just did this experiment - pulled my July month in the “classic” reports in Chrome, checked memory in its task manager - 118MB. Then did the same in the “reimagined” reports, it is slow… wait for it… slow… wait for it… loaded. 685 MB!