2022-11-21 - @sagarkothari88's Development 📲 Update
Dealing with Apple.
- Apple is asking many questions & giving many reasons to reject the app.
- I am responding them with concrete answers.
- There is too much of back and forth going on.
- Over emails, over AppStoreConnect.
- I'll keep you posted on the Outcome.
- So, far app is in the rejected state & I am trying my best to convince them.
- Refer screenshot above
@forkyishere wants to set a custom RPC node.
- Thank you @forkyishere for providing feedback.
- This feature was integrated earlier & removed.
- I added it back.
Here are the screenshots for your reference.
Step 1 - Settings > Change Server > Custom
Step 2 - Enter URL of RPC node & Hit Save.
Step 3 - Confirm that it's updated & refresh the feeds
What's next?
- Continue fighting with Apple
- Submit them new builds with changes that they have suggested.
Vote me as witness | Download iOS App | Download Android App |
---|---|---|
2022-11-21 - @sagarkothari88's Curation ❤️ Report
- My curation bot (or I've) decided to ❤️ love the posts of following users.
- Don't forget to motivate below mentioned users by clicking the links provided.
Vote me as witness | Download iOS App | Download Android App |
---|---|---|
Cheers
Have a good one
Thanks for choosing my post🧡
You're welcome @obikay.
Now we are talking, hehehe =)
If the reason for removal was because you want to implement a round-robin mechanism or a next-on-failure... then you can just disable custom ones for that "behavior". Or later on, if in a more elaborate solution, add scoring to how effective or fast each RPC node is responding and then score the list in time (last 5 min or so, or configurable), so that the app can always get the best RPC no matter which ones are on the list.