Result buffer too small for 3582 bytes of A-GNSS data

[robotcux]

Hi all,

I started encountering the error shown in the attached screenshot.

From the this PR , it seems the issue is new and that the PR is aimed at resolving it. However, I am trying to understand the best steps to take now.

Here are my questions:

1. Is this error a blocker for using the AGNSS feature?
2. Does the mentioned PR fully resolve the issue?
3. If the PR resolves the problem, how can I apply the fix to my project?
4. I am currently using SDK version 2.7.0. Should I upgrade to a newer version?
5. Is there a way to fix the issue without changing the SDK version?

For context:

• The SDK version I am using is 2.7.0.
• I use the AGNSS feature of the nRF Cloud.
• My chip is the nRF9161.

Thank you for your support!

Best regards,

[dejans]

Hi,

Can you provide some information about your application?

Can you provide full error log?

Best regards,
Dejan

[robotcux]

You can use the location sample from the sdk-nrf. Simply, I use AGNSS location service. There is no extra log. 

[dejans]

Hi,

Unfortunately, in your case A-GNSS cannot be used without applying the change from mentioned PR. The buffer was originally small for getting the data from all satellites. I would expect that your issue gets fully resolved after applying the fix. The best way to apply changes would be to cherry-pick this commit. Minimal solution is to increase AGNSS_REQUEST_RECV_BUF_SIZE in lib/location/method_gnss.c.

Best regards,
Dejan 

[robotcux]

Hi Dejan,

Thank you for the clarification.

However, shouldn’t this issue have been flagged in the documentation or release notes for the previous versions? Considering the impact, wouldn’t this qualify as a significant issue? From my perspective, it raises concerns about the reliability of the current version.

Looking forward to your thoughts.

[dejans]

Hi,

robotcux said:

shouldn’t this issue have been flagged in the documentation or release notes for the previous versions?

As far as I know, this problem was not known issue when previous releases came out. As you already know, this PR is very recent.

robotcux said:

Considering the impact, wouldn’t this qualify as a significant issue?

I agree that it might be considered significant, but there was no impact so far. As mentioned previously, this issue might happen only in cases where data is received from all satellites.

robotcux said:

From my perspective, it raises concerns about the reliability of the current version.

You should not be concerned with the PR now in place. Additionally, you can always open new ticket for any potential issue that you might have in the future.

Best regards,
Dejan