We have not integrated Iyzico and PayTR payment methods into our system as of now. We will add in future updates. However, if you need a payment method specific to your country urgnetly, we can customize it for you.

We need it integrated, if you release an update after customizing it, I can buy it.

When are you planning to buy this product?

There is currently a discount, I can buy it now, how long will the discount continue? Also, payments need to be revised according to the PAYTR MARKETPLACE module. Because this is the marketplace.

Our sale ends on July 20, 2024. Currently, we have not added the PAYTR payment gateway to our project. We will consider adding it in future updates.

If you have already purchased it, can you give me a contact number where I can get help? Can you email the numbering to beritankorkusuz7635@gmail.com?

Do you want to customize your project?

We will provide an update so you will get all the bug resolved in the updated code.

Yes, all features that are provided are working out of the box. It’s just that you have to setup them properly one time. We are there if you get stuck in setup so don’t worry about that.

Ok, which plan do you need to test all the features on Firebase? Is Spark enough?

Yes, Spark plan is enough for basic usage. You can observe your usage and convert into Blaze plan if needed.

@mirdo commented that his google sign in is not working after logging out but i checked the demo and logged in and logged out tried log in again i got msg ( you are not a valid user) ? i’m really confused which version is stable with google sign in ? when this gonna be fixed ?

Can you please share a video recording? Because Google sign in is working without any issue in the latest version.

I tried with my gf gmail account it login in and logout and i can relog in again but as soon as i update the profile with info , country , number.. and log out try to re log in it throw this error msg you are not a valid user, basically it’s useless google log in if the user can’t update his address and number… for booking.

Okay, we will fix it the next update. Thanks for notifying.

I think you should release a stable version with updated documentation that everyone can buy and use than betas and nightly released version and getting help from the buyers community to track bugs, working this way you would be the best seller in here and you would sell thousands of templates apps

I think you should release a stable version with updated documentation that everyone can buy and use than betas and nightly released version and getting help from the buyers community to track bugs, working this way you would be the in here and you would sell thousands of templates apps

Ps: sorry duplicate comment I must have pressed twice

Thank you for your valuable feedback. We appreciate your suggestions and understand the importance of releasing a stable version with updated documentation.

Our goal is to provide a high-quality product that meets the needs of our users. We are actively working towards a stable release and are committed to improving our documentation to ensure a seamless experience for our buyers.

Hi I tried to use OTP to register in demo app but I’m facing a problem here After getting the code from firebase it redirects me to registration screen, Name…, username ( phone number can’t be edited) Email .. Than registered got msg link sent to verify your email once email verified it redirects me to the web homepage ? My question how do you login afterwards? In registration page it was no password to fill up ?

Sorry just remember something in you documentions you’re adding rule for firebase database ? Do we need database for google or OTP authentication ? I think we dont, once data are registered in backend database it’s enough otherwise the cost will be higher with firebase database

When a user login in via social login, we do not show the password field. At that time, we set the password as the user’s phone number or email. Please note that the username cannot be changed when a user login in via social login.

We use the Firebase database for chat features.

But when registering with OTP it dosen’t redirect me to my profile page ? it just go back to the login page for the user it might create confusion about what to do next, also when updating profile on OTP once logged in and then logout and try login again same error happened with google sign in ( user error msg)

We’ve attached a video link for logging in with mobile. Please refer to this link to login with your mobile device:

Video Link: https://drive.google.com/file/d/1JESx0TWMhZc82Omu7_omL7QgBmcwa_NO/view?usp=sharing

Regarding the login error, we’ve fixed the issue and will include this fix in the next update.

Thanks, i meant you have to register on OTP then logging again instead of registering and redirect you to your profile straight away , because sending twice code on Firebase will cost more money

Thanks again for replying

Thank you for your suggestion. We’ll be working on reducing the need to send the OTP twice and aim to send the OTP only once before redirecting to the main screen.

Also the You are able to register without accepting the TOS

Yes, will fix this in next update.

Cool, ready to buy when you will fix those issues

1- One thing i want know in your demo backend there is an option to add Firebase web api key ? but in firebase Cloud Messaging API (Legacy) key is deprecated?

2- also using the demo user app to test functionalities sometimes i get overflow errors pixels using my Iphone x ?

1) Yes, it’s deprecated. We are actively working on the Cloud Messaging features. We will resolve this issue and provide an update in the next release.

2) Could you please share the details of which screen you are encountering the overflow error on? We’ll fix it and include the update in the next release.

1 – basically the place holder for the api web key in backend is just dummy it’s not working ? and what it used for ? ios notifications or android notifications ?

2- it was withe my iphone x ( 15.1) when booking the go to booking-> provider details

1) Firebase notifications work in the old account because they already provided the server key. However, we need to migrate to a new account since those places do not provide the server key in the new account.

2) Could you please share the screenshot? This will help us easily identify and resolve the issue.

1- so basically if I buy the template now the notifications won’t work because my firebase account doesn’t provide the old key it says deprecated

2- my bad my iphone setting was on view -zoom and it created the issue but once I reverted to standard view the issue vanished from the app, but it’s interesting issue to fix maybe in case someone use zoom setting on their phone

Yes, We do offer comprehensive assistance with the installation process, including setting up the app on the App Store, Play Store, and the web. If you want a complete installation, you can purchase the extended license or if you buy regular license then you can purchase our installation service.

You will need to buy hosting server where your website will be hosted and they will provide email service as well.

If you have any specific preferences or requirements for these services, please let us know, and we can provide more detailed recommendations.

Feel free to reach out with any more questions or for further assistance. We’re here to help!

how much extra i need to pay for installation service ?

Please visit our service pack here: https://service.iqonic.design/services/handyman-app-full-setup-and-configuration/

sorry to bother you . but i have one more question . what should i buy from google play console individual or business ??? thanks .

We’ve checked our app, and all functions are working properly. However, if you encounter any issues, please don’t hesitate to generate a ticket. Our team will promptly address and resolve any issues you may encounter.

Link: https://iqonic.desky.support/

Ticket has been generated but no response has been given. Please check again the issues I mentioned in the demo app you provided. Let’s take a look at the above mentioned (1& 2)issues.

Handyman app has lot of features and function but there are always errors or bugs when release new updates.

A customer still needs new features and functions more than just a error or bug-free update.

This is the 5th time that I have updated by paying money to Freelance Developer The latest launched update is also have errors or bugs.

If the ticket is generated, they don’t get any reply, but once they get it, they say to update the latest code They should either correct the errors/bugs from seller side or seller will update the new code on buyer’s server without any cost Because that errors/bugs on the seller’s side that they have to fix

We replied to ticket #20323 three days ago. Please check that ticket and reply there for further communication.

The issue is still not resolved

Have you posted any screenshot or error log what is not working in your any one ticket?

I have shared the error log screen recordings and screenshot to you twice but you have not responded yet

In which ticket you have shared any screenshot for above mentioned errors?

28/06/2024 date, # 20571 Ticket No. Screen shots and screen recording have been shared.

You haven’t shared any screenshots or recordings in ticket #20571, but we did find one screenshot in your previous ticket #20323. It appears that you haven’t updated the source code to the latest version. We have already fixed these two issues a long time ago. Kindly update your code to the latest version.

I have shared the screen recording of the shared screenshot,recordings and error logs as # 20635 in the ticket.

The latest updated code also has errors

1.Newly added category is not shown on user app home page except default category. 2.The booking is not complete when a customer has booked the service as a package for which provider has made an advance payment .

1. You can change your category from frontend settings in Admin Panel.

2. Okay, we will check in our system flow and let you know.

Cloud Messaging API (Legacy)Enabled

If you are an existing user of the legacy HTTP or XMPP APIs (deprecated on 6/20/2023), you must migrate to the latest Firebase Cloud Messaging API (HTTP v1) by 6/20/2024.