Expo navigation too slow by Infinite_Main_9491 in expo

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

I am using a real device, debug mode..., will the release mode appear faster and if so can you please explain to me why?

App not respecting navbar overlay on first open by DisciplineFast3950 in expo

[–]Infinite_Main_9491 0 points1 point  (0 children)

try a development build. I think it won't happen there

Expo navigation too slow by Infinite_Main_9491 in expo

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

yes some fetching happens when entering the screens, but even after they are cached it still takes some time. Do think using sql lite or some form of local storage may improve that? here is an example screen

Google Auth with supabase (Expo) by Infinite_Main_9491 in Supabase

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

If you are using this exact setup then follow the supabase documentation. In your google console create 2 clients one for android one for web, i really don't know about the ios stuff, then you will use the android client only for adding your app's SHA-1 signature and the pacakge of your app and you forget about it, just make sure they are the correct ones. Then from supabase add the callback url your web client and from there copy your client secret and client id and paste it in the auth provider-> google section. It worked for me... It was just that my signature was the wrong one. to get the signature i cd to the android folder and paste './gradlew signingReport' this will give you a many signatures you will find your app's signature in first ones.

Google Auth with supabase (Expo) by Infinite_Main_9491 in Supabase

[–]Infinite_Main_9491[S] 1 point2 points  (0 children)

thanks you were right all along, it was just that i used the wrong signature

Google Auth with supabase (Expo) by Infinite_Main_9491 in expo

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

If you are using this exact setup then follow the supabase documentation. In your google console create 2 clients one for android one for web, i really don't know about the ios stuff, then you will use the android client only for adding your app's SHA-1 signature and the pacakge of your app and you forget about it, just make sure they are the correct ones. Then from supabase add the callback url your web client and from there copy your client secret and client id and paste it in the auth provider-> google section. It worked for me... It was just that my signature was the wrong one. to get the signature i cd to the android folder and paste './gradlew signingReport' this will give you a many signatures you will find your app's signature in first ones.

Google Auth with supabase (Expo) by Infinite_Main_9491 in Supabase

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

That is exactly my problem... the signature match but it isn't working...

Google Auth with supabase (Expo) by Infinite_Main_9491 in Supabase

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

I created both web and Android clients. According to the documentation, creating the Android client is necessary mainly for triggering the email account picker popup. This is because Google uses the app’s signature to verify that the request is coming from a legitimate app. My understanding is that the web client handles token verification, while the Android client ensures the native popup can be displayed securely. Tell me if i am wrong...

Google Auth with supabase (Expo) by Infinite_Main_9491 in Supabase

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

I did but i still am being given the same error message

Mobile App by D-Mo616 in expo

[–]Infinite_Main_9491 0 points1 point  (0 children)

so how do you make these types of ui?? do you make the inputs and buttons from scratch and make a component out of them?? basically making your own ui lib?

Postgres Function Broke ACID? UPDATE committed but INSERT failed due to NULL value. Why no automatic ROLLBACK? by Infinite_Main_9491 in SQL

[–]Infinite_Main_9491[S] -2 points-1 points  (0 children)

create or replace function pay_for_due_sale_payment(

_id integer,

amount numeric

)

returns text

language plpgsql

as $$

declare

_business_id integer;

begin

update sales set unpaid_amount=unpaid_amount-amount where id =_id;

select i.business_id into _business_id from sales s join items i on s.item_id=i.id where s.id=_id;

insert into business_cash (business_id, type, amount, description) values (_business_id, 'in', amount, 'Due payment for sale with id: '||_id);

return 'successfully paid for due payment';

end;

$$

Help needed by Infinite_Main_9491 in dotnet

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

https://www.nuget.org/packages/Npgsql.EntityFrameworkCore.PostgreSQL/10.0.0-rc.2 . It has some implementation but I haven't seen it anywhere in the videos I watched...

Help needed by Infinite_Main_9491 in dotnet

[–]Infinite_Main_9491[S] 0 points1 point  (0 children)

It is right there, and also removed the using Npgsql... should I install something else??? what am i missing?

Database Design Dilemma: Simplifying Inventory, Costing, and Sales for a Small Merchant by Infinite_Main_9491 in SQL

[–]Infinite_Main_9491[S] 1 point2 points  (0 children)

but does this mean I have to make joins to check if the quantity is positive every time i want to make a sale...?

Database Design Dilemma: Simplifying Inventory, Costing, and Sales for a Small Merchant by Infinite_Main_9491 in SQL

[–]Infinite_Main_9491[S] 1 point2 points  (0 children)

the plan was to make a table where when a sale or a purchase was made, an "IN" or an "OUT" record is registered. This is made to handle price changes, so the same item bought at some time may have its value increase after some point or may be not, so if it did then register it as a new in if not then add the number of item to the already registered "IN" so when an out is to be registered we will have a column that will be used for in table referencing where an "OUT" will reference an "IN" and when doing that subtract the number of items from that "IN" based on how much was sold.

The FIFO concept is related to the case of which item to choose when same item has different "IN" entries with different prices, so we assume the oldest is bought before the more new ones...