[Nishit Shan]

in reply to: Carrier Lookup API #14504

Hello Andrey,

Kindly use the PayPal ID ceo@siliconinfo.com for all future payments.

[Nishit Shan]

in reply to: Carrier Lookup API #14503

Hello Andrey,

Important Notice:
Please do not process any payments to the current PayPal ID info@siliconinfo.com
for the time being. A new PayPal ID will be provided to you shortly.

[Nishit Shan]

in reply to: Messenger App #14502

Hello Andrey,

Please check the message from mobile App team :

Please look at our comments for your queries.
1.Once Friends APP development complete would you provide a support for the work if bugs / conflicts have been occurred?
2.The APP is integrated with WP Guppy messenger plugin if the WP Guppy Plugin got updated and as a result some conflicts with the APP will you be willing to provide us a support on re – config / sync support?
3.Does the APP rely on any third party connectors that may affect its proper functionality / connectivity?
Comments: As you are aware, Apple and Google frequently updates its operating systems and hardware, which can sometimes result in incompatibility with existing app libraries and coding frameworks. Since neither Apple nor Google provide guarantees regarding when they may deprecate certain libraries, it becomes necessary to periodically upgrade the app to ensure continued compliance and compatibility with their latest policies.

I also discussed this matter with Mr. M. V. Rupesh, and considering our long-term relationship, he has kindly agreed free support period to three months and upgrades at no additional cost during this time.

[Nishit Shan]

in reply to: Carrier Lookup API #14501

Hello Andrey,

Please find #post-14500 .

[Nishit Shan]

in reply to: Carrier Lookup API #14498

Hello Andrey,

I understand your frustration about the bulk edit delay, but you also need to understand that I have to review almost all of the code before making even a small change. I need to check for possible variable conflicts, function conflicts, and even when modifying a view template, I must ensure that no pre-existing tag IDs are duplicated. This process takes time, but it’s mandatory because I want to avoid any conflicts. I follow this practice every time, which is why task completion or bug fixing may take longer. I hope you will understand.

[Nishit Shan]

in reply to: Carrier Lookup API #14495

Hello Andrey,

I am activating multiple selection for the brand in bulk edit by checking the code .

Message from mobile app team:
Thank you for sharing your detailed feedback. I completely understand your concern regarding the budget and your preference to repair the existing source code rather than investing in a full redesign.

The assessment is that the required repair and upgrade work cannot be completed within the current proposed budget + additional $500. As per the evaluation, the minimum budget needed to proceed with this task is $1250. This amount ensures that the team can deliver the repaired and upgraded app along with the updated source code, as well as the required APK and iOS build files.

[Nishit Shan]

in reply to: Carrier Lookup API #14492

Hello Andrey

For the multiple selection on bulk edit there is currently no function for that, drop-down was also not here before.There was no error or conflict i found for the bulk edit brand selection instead there was no function which support brand selection. I am checking the rest of the code and also my backup code will find more then update you .

Message from mobile app team:
I want to share transparently that the current budget is too low for this Changes & upgrade. Given the work involved in updating the project to target API level 35, performing necessary code refactoring, testing, and ensuring Play Store compliance, the minimum budget required is $1500.

This will allow us to complete the upgrade properly and ensure the Friends app continues to meet Google’s requirements without any disruptions.

[Nishit Shan]

in reply to: Carrier Lookup API #14486

Hello Andrey,

Please find #post-14484

[Nishit Shan]

in reply to: Carrier Lookup API #14484

Hello Andrey,

I have checked the code thoroughly and can confirm there was no error or broken functionality. What I found is that the brand selection was implemented using an input field, not a select dropdown. There was no instruction in the task mentioning that it should be a select tag instead of an input field, and it also did not occur to me at that time that a select tag might be expected.Check this link for completed task reference https://excellentnumbers.com/temp_vid/Screencast%20from%202025-09-29%2011-44-09.mp4

Regarding your question about whether any other developer is working on this site, I want to be completely honest: even if I wanted to hand this over to another developer, it would not be practical. The code structure is quite complex, and another developer would take significantly more time—perhaps 10 days for a task that normally takes 1 day. That would not be beneficial for either of us.

• This reply was modified 1 month, 1 week ago by Nishit Shan.

[Nishit Shan]

in reply to: Carrier Lookup API #14482

Hello Andrey,

I am currently checking the error, and I kindly request that the recent changes not be blamed for breaking any previous tasks. I always make sure to thoroughly test the functionality before implementing any changes, and I take extra care to ensure that nothing in the existing system or scripts is affected. This is also why even small fixes may take some time.

If any issue arises, it might be due to a missing script or because the functionality was not fully tested earlier. I would again request that tasks be tested thoroughly before closing them, as I do not want to repeatedly face such blame.

That said, I will do my best to fix the existing bug as soon as possible, and I will also ensure that the carrier lookup API is properly linked in the API integration section of the user’s account page.

I hope you will understand me.

[Nishit Shan]

in reply to: Carrier Lookup API #14473

Hello Andrey,

I’ll give the final touch to the Carrier Lookup task and review the task description for verification. For the Friend-App task, the developer will handle both the repair and upgrade points. However, I’m not able to see the budget on the task page. Could you please update it again so I can inform my team and they can proceed with the next steps?

[Nishit Shan]

in reply to: Carrier Lookup API #14462

Hello Andrey,

Please add a new task on my page with your budget so the team can proceed with the mobile app task. Regarding the Carrier Lookup API, it has been completed. After testing, I just need to give it a finishing touch, which will hardly take a day.

[Nishit Shan]

in reply to: Carrier Lookup API #14460

Hello Andrey,

Update for Mobile App: The complete development will take 30 working days .

[Nishit Shan]

in reply to: Carrier Lookup API #14459

Hello Andrey,

I have listed the API stats on the admin side. You can view them by navigating to Home → Statistics → Carrier Lookup API Stats.
Additionally, you can check the updated API documentation page by logging in and visiting the following URL:
https://excellentnumbers.com/account.php?action=carrier-lookup-api-integration.

[Nishit Shan]

in reply to: Carrier Lookup API #14457

Hello Andrey,

I am integrating the stats view on the admin side so they can monitor it. Stats management is the only task pending, and once it’s done, everything else will be complete. I’ll update you on the progress or once it’s completed.

[Author]

Posts